[
https://issues.apache.org/jira/browse/MYFACES-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603267#comment-15603267
]
Leonardo Uribe commented on MYFACES-4068:
-----------------------------------------
There is a change done in 2.2.10 that maybe could be related. See MYFACES-3904
for details. I think the changes done are justified, but if the listener is not
working it could be because the decode of h:selectManyCheckbox is not catching
the events properly. Could you please try with f:ajax instead and see if the
same behavior happen, to discard p:ajax malfunction?
> Ajax-Listener (PrimeFaces) is not called for some selection-components
> ----------------------------------------------------------------------
>
> Key: MYFACES-4068
> URL: https://issues.apache.org/jira/browse/MYFACES-4068
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.2.10, 2.2.11
> Environment: MyFaces 2.2.10/2.2.11 on Wildfly 9.0.2, PrimeFaces 5.3
> or 6.0
> Reporter: Bernhard Hablesreiter
>
> Recently we ran into some problems getting a PrimeFaces "p:ajax"-Component
> attached to a h:selectManyCheckbox or h:selectOneRadio.
> The problem here is, that the specified "listener"-action is not called.
> We first thought this is a PF issue but in only started with version 2.2.10
> of MyFaces. In Version 2.2.9 it worked just fine and propably a default
> jsf-ajax-listener won't work as well (not tested though).
> E.g. we have this non-working code where the listener action is not called
> (no matter what event-type we specify):
> {code:xml}
> <h:selectManyCheckbox layout="pageDirection" value="#{bean.mySelection}">
> <f:selectItems value="#{selectionItems}" />
> <p:ajax process="@this" listener="#{myBean.selectionChanged}"
> update="@form" global="false" />
> </h:selectManyCheckbox>
> {code}
> We're not sure if this should be fixed on PF side, but as mentioned before,
> the problem started with the switch to MyFaces 2.2.10.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
