Leonardo Uribe created MYFACES-3960:
---------------------------------------
Summary: AjaxBehaviorEvent should be queued before ActionEvent
Key: MYFACES-3960
URL: https://issues.apache.org/jira/browse/MYFACES-3960
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314, JSR-344
Affects Versions: 2.2.7, 2.1.17, 2.0.23
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
>From Bauke Scholtz
Trigger:
http://stackoverflow.com/q/28901284
Code:
<h:commandLink action="#{bean.action}">
<f:ajax listener="#{bean.listener}" />
</h:commandLink>
Mojarra:
Listener is first invoked and then action.
MyFaces:
Action is first invoked and then listener.
Who's correct? I couldn't find this in the spec. We need to align out it. As
the action is supposed to be definitive (because of the navigation case
outcome), I find Mojarra behavior is correct.
It looks like an exception to the general rule (decode and then decode client
behaviors), so we need to decode, decode client behaviors and queue ActionEvent
at last.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
