[richfaces-issues] [JBoss JIRA] Resolved: (RF-8435) a4j:actionParam: unnamed parameters don't work in JSF2
Nick Belaevski (JIRA)
jira-events at lists.jboss.org
Thu Feb 25 07:46:10 EST 2010
[ https://jira.jboss.org/jira/browse/RF-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Belaevski resolved RF-8435.
--------------------------------
Resolution: Won't Fix
Won't fix: "name" is mandatory, so it should be set.
> a4j:actionParam: unnamed parameters don't work in JSF2
> ------------------------------------------------------
>
> Key: RF-8435
> URL: https://jira.jboss.org/jira/browse/RF-8435
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF 2.0
> Affects Versions: 3.3.3.CR1
> Reporter: Nick Belaevski
> Assignee: Nick Belaevski
>
> Details are on forum. The issue is caused by the fact that JSF 2.0 doesn't store clientId in state anymore while JSF 1.2 used that. So, instance of ActionListener provided by a4j:actionParam component uses clientId when name isn't defined, however it cannot properly re-create clientId on postback, as the component is not in view anymore (parent = null).
> Code to reproduce:
> <rich:dropDownMenu value="Menu1">
> <rich:menuItem>
> <a4j:actionparam assignTo="#{forum5Bean.selection}" value="1223" />
> </rich:menuItem>
> </rich:dropDownMenu>
--
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
More information about the richfaces-issues
mailing list