according to the docs:
it depends on what mode the autocomplete is operating. The parameter is ignored for client and lazyClient modes. In what mode operates your autocomplete please?
Yes, its cachedAjax. Also my component only allows ajax and cachedAjax modes via a switch parameter.
The only thing I can think of is that this is all due the abstract class I am using. As you can see the parameter "bean" is of a specific type. That is an abstract class type. The autocomplete then calls functions from abstract class, one of them autocompleteMethod(String q). But since the object passed is an instance of a type that extends abstract class ... well maybe that confuses binding operation and it thinks my function doesn't have a parameter. I will try with 4.2.2, maybe it a new bug or something.
Anyway this is just a refactor of an old autocomplete template component that worked just fine, but was cumbersome to use since you had to pass in a whole pile of redundant parameters. Now I wanted to encapsulate all that stuff in one abstract class but this is a show-stopper...
Anything else I could check regarding this before assuming the worst and reverting to that old version ?
My own stupidity.
Interesting behaviour though Took me 2 days to figure it out. Everything else worked fine that is. Until I loaded a4j:log and that didn't work either... that made me think a bit.