-
1. Re: rich:autocomplete problem: autocompleteMethod is called without the prefix
jhuska Oct 16, 2012 6:38 AM (in response to neikius)Hi,
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?
-
2. Re: rich:autocomplete problem: autocompleteMethod is called without the prefix
neikius Oct 16, 2012 7:48 AM (in response to jhuska)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 ?
-
3. Re: rich:autocomplete problem: autocompleteMethod is called without the prefix
neikius Oct 17, 2012 9:16 AM (in response to neikius)My own stupidity.
Missing h:form
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.