[richfaces-issues] [JBoss JIRA] Commented: (RF-8435) a4j:actionParam: unnamed parameters don't work in JSF2

Ilya Shaikovsky (JIRA) jira-events at lists.jboss.org
Wed Feb 24 05:03:17 EST 2010


    [ https://jira.jboss.org/jira/browse/RF-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12516270#action_12516270 ] 

Ilya Shaikovsky commented on RF-8435:
-------------------------------------

name attribute declared as mandatory in 3.3.x also.

> 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