Rogerio Pereira schrieb: > But focus component only generates JS code that is executed by browser > setting the focus on specified component, the MyFaces Ajax execute JS > code generated on the server? > That does not make a difference in case of compound components. Components can use internal ids for edit fields etc... and the form handling can be mapped to those ids, for instance more complicated components use hidden fields, for the form traversal and other constructs for the visualisation.
Now if such a component is targettet by a focus code, it simply cannot work because the hidden id gets the focus (as an example) while some editable div does the action. I do not see a way out of this for components which influence the dom tree to a certain effect than to introduce an api on javascript level which allows the components themselves to expose their internal stuff.
