[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ] Valiantsin Shukaila edited comment on RF-11469 at 6/13/13 7:15 AM: ------------------------------------------------------------------- I am having such problem with 4.3.1 version of Richfaces. The Problem is that by default autoCompleteMethod seems to be defined with 3 parameters: FacesContext,UIComponent,String. This can be seen from AutocompleteRendererBase class, getItems method: {code} try { // String value = getInputValue(facesContext, component); itemsObject = autocompleteMethod.invoke(facesContext.getELContext(), new Object[] { facesContext, component, value }); } catch (MethodNotFoundException e) { ExpressionFactory expressionFactory = facesContext.getApplication().getExpressionFactory(); autocompleteMethod = expressionFactory.createMethodExpression(facesContext.getELContext(),autocompleteMethod.getExpressionString(), Object.class, new Class[] { String.class }); itemsObject = autocompleteMethod.invoke(facesContext.getELContext(), new Object[] { value }); } {code} One can see that if method with 3 arguments is not found(actually it is not clear why it is 3 arguments, they are useless) just exception is caught and new MethodExpression is created. But this new MethodExpression doesn't take in account all facelet compositions so beans passed as parameters would not be resolved in this new method expression. So I see the easiest workaround for this: change method declaration in the bean so that it would have 3 arguments (FacesContext, UIComponent, String). For me this worked well. Actually it's a pity that almost 2 years passed after this issue was found and it is still not resolved. Actually I have such a bad feeling with all richfaces 4 version. Seems nobody supports it now? was (Author: Trims): I am having such problem with 4.3.1 version of Richfaces. The Problem is that by default autoCompleteMethod seems to be defined with 3 parameters: FacesContext,UIComponent,String. This can be seen from here: {code} try { // String value = getInputValue(facesContext, component); itemsObject = autocompleteMethod.invoke(facesContext.getELContext(), new Object[] { facesContext, component, value }); } catch (MethodNotFoundException e) { ExpressionFactory expressionFactory = facesContext.getApplication().getExpressionFactory(); autocompleteMethod = expressionFactory.createMethodExpression(facesContext.getELContext(),autocompleteMethod.getExpressionString(), Object.class, new Class[] { String.class }); itemsObject = autocompleteMethod.invoke(facesContext.getELContext(), new Object[] { value }); } {code} One can see that if method with 3 arguments is not found(actually it is not clear why it is 3 arguments, they are useless) just exception is caught and new MethodExpression is created. But this new MethodExpression doesn't take in account all facelet compositions so beans passed as parameters would not be resolved in this new method expression. So I see the easiest workaround for this: change method declaration in the bean so that it would have 3 arguments (FacesContext, UIComponent, String). For me this worked well. Actually it's a pity that almost 2 years passed after this issue was found and it is still not resolved. Actually I have such a bad feeling with all richfaces 4 version. Seems nobody supports it now? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira