[
https://issues.apache.org/jira/browse/MYFACES-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420599#comment-13420599
]
Leonardo Uribe commented on MYFACES-3582:
-----------------------------------------
Sounds something related to MYFACES-3383, which was solved recently. In theory,
the problem could be related to the resolution of targets attribute,
<composite:clientBehavior name="change" event="change"
targets="#{cc.clientId}:some-id-here"/>
The #{cc.clientId} seems to be unnecessary, but I don't know the details behind
that.
Anyway we need first to try if the latest code solves the problem, and later if
the error persists, a more simplified/detailed test case. Otherwise, there is
no way to advance further.
> Unable to process ajax calls within nested Composite Components
> ---------------------------------------------------------------
>
> Key: MYFACES-3582
> URL: https://issues.apache.org/jira/browse/MYFACES-3582
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.1.8
> Environment: Windows 7, Eclipse - Indigo Service Release 2,
> Chrome/Firefox 13
> Reporter: Emil Petkov
>
> I am unable to make ajax calls within nested Composite Components. The outer
> composite could be just a wrapper. For the issue to appear it could be empty
> with only <composite:insertChildren/> in it.
> The inner composite component uses
> <composite:clientBehavior name="change" event="change"
> targets="#{cc.clientId}:some-id-here"/>
> The event actually doesn't matter.
> The inner component receives an ajax call like this:
> <controls:listBox
> property="#{carDetailsMediator.carDetailsCarMakesListBoxProp}"
> items="#{carDetailsMediator.carDetailsCarMakesListBoxSelectItems}"
> customId="carMakes" width="115" visibleLines="6">
> <f:ajax event="change" render=":formID:carModel:combobox"
> listener="#{carDetailsMediator.changeCarMake}"
> onevent="initComboboxes" />
> </controls:listBox>
> I tried to debug the myFaces 2.1.8 implementation and got to the point where
> in the lifecycle of the process at step 5 - Invoke Application there were no
> events and therefore no listeners were called.
> I tried the same setup, but without the outer Composite Component, everything
> worked - the correct event was fired and the listeners called.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
