[richfaces-issues] [JBoss JIRA] Updated: (RF-8215) <f:actionParam> is invoked on INVOKE_APPLICATION phase rather than UPDATE_MODEL_VALUES phase when used inside a jsFunction

[George Gastaldi (JIRA)]

     [ https://jira.jboss.org/jira/browse/RF-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi updated RF-8215:
--------------------------------

    Description: 
The documentation in http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf?c=actionparam&tab=usage and http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/a4j_actionparam.html states that the property assigned in the "assignTo" attribute is set in the UPDATE_MODEL_VALUES phase.

By using a jsFunction with an actionParam, it is possible to see that the assignment is done on the INVOKE_APPLICATION phase, thus calling the actionListener defined in the jsFunction

Example:

<a4j:jsFunction name="myJsFunction" actionListener="#{myBean.myActionListener}" >
     <a4j:actionparam name="param1"assignTo="#{myBean.paramName}" />
</a4j:jsFunction>

Calling: myJsFunction('Any Value') does the trick. The ActionListener will be called BEFORE the assignment of the actionParam

  was:
The documentation in http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf?c=actionparam&tab=usage and http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/a4j_actionparam.html states that the property assigned in the "assignTo" attribute is set in the UPDATE_MODEL_VALUES phase.

By using a jsFunction with an actionParam, it is possible to see that the assignment is done on the INVOKE_APPLICATION phase, thus calling the actionListener defined in the jsFunction

Example:

<a4j:jsFunction name="myJsFunction" actionListener="#{myBean.myActionListener}" >
     <a4j:actionparam name="param1"assignTo="#{myBean.paramName}" />
</a4j:jsFunction>

Calling: myJsFunction('Any Value') does the trick. The ActionListener will be called AFTER the assignment of the actionParam



> <f:actionParam> is invoked on INVOKE_APPLICATION phase rather than UPDATE_MODEL_VALUES phase when used inside a jsFunction
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-8215
>                 URL: https://jira.jboss.org/jira/browse/RF-8215
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 3.3.2.SR1
>            Reporter: George Gastaldi
>
> The documentation in http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf?c=actionparam&tab=usage and http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/a4j_actionparam.html states that the property assigned in the "assignTo" attribute is set in the UPDATE_MODEL_VALUES phase.
> By using a jsFunction with an actionParam, it is possible to see that the assignment is done on the INVOKE_APPLICATION phase, thus calling the actionListener defined in the jsFunction
> Example:
> <a4j:jsFunction name="myJsFunction" actionListener="#{myBean.myActionListener}" >
>      <a4j:actionparam name="param1"assignTo="#{myBean.paramName}" />
> </a4j:jsFunction>
> Calling: myJsFunction('Any Value') does the trick. The ActionListener will be called BEFORE the assignment of the actionParam

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira