[
https://issues.jboss.org/browse/RF-11446?page=com.atlassian.jira.plugin.s...
]
Brendan Healey updated RF-11446:
--------------------------------
Description:
In the following scenario when the jsTest() function is called then in
the server log I see the jsTestAction method executing before the
setJsTestParam method, so the parameter supplied by a4j:param is useless.
<a4j:jsFunction name="jsTest"
oncomplete="alert(event.data)"
actionListener="#{bean.jsTestAction}"
data="#{bean.jsTestData}">
<a4j:param name="p1" value="Fred"
assignTo="#{bean.jsTestParam}"/>
</a4j:jsFunction>
The workaround is to use action= rather than actionListener, but this
is a pretty fundamental issue and ought to be fixed IMHO.
was:
In the following scenario when the jsTest() function is called then in
the server log I see the jsTestAction method executing before the
setJsTestParam method, so the parameter supplied by a4j:param is useless.
<a4j:jsFunction name="jsTest"
oncomplete="alert(event.data)"
actionListener="#{bean.jsTestAction}"
data="#{bean.jsTestData}">
<a4j:param name="p1" value="Fred"
assignTo="#{bean.jsTestParam}"/>
</a4j:jsFunction>
The workaround is to use action= rather than actionListener, but this
is a pretty fundamental issue and needs to get fixed IMHO.
a4j:jsFunction actionListener= method called before a4j:param
assignTo setter
-----------------------------------------------------------------------------
Key: RF-11446
URL:
https://issues.jboss.org/browse/RF-11446
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: Mojarra 2.1.3
Reporter: Brendan Healey
In the following scenario when the jsTest() function is called then in
the server log I see the jsTestAction method executing before the
setJsTestParam method, so the parameter supplied by a4j:param is useless.
<a4j:jsFunction name="jsTest"
oncomplete="alert(event.data)"
actionListener="#{bean.jsTestAction}"
data="#{bean.jsTestData}">
<a4j:param name="p1" value="Fred"
assignTo="#{bean.jsTestParam}"/>
</a4j:jsFunction>
The workaround is to use action= rather than actionListener, but this
is a pretty fundamental issue and ought to be fixed IMHO.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira