[richfaces-issues] [JBoss JIRA] (RF-12712) Upgrade to Mojarra 2.1.17

[Lukáš Fryč (JIRA)]

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

Lukáš Fryč commented on RF-12712:
---------------------------------

There is change log for Mojarra {{2.1.17}}: http://java.net/jira/browse/JAVASERVERFACES/fixforversion/16239

However I can't see anything which was fixed there related to this issue other than ViewScoped fixes:
http://java.net/jira/browse/JAVASERVERFACES-2656
http://java.net/jira/browse/JAVASERVERFACES-2638
http://java.net/jira/browse/JAVASERVERFACES-1706

Pavol is investigating if changing holding attributes in SessionScoped with {{2.1.16}} fixes the issue.
                
> Upgrade to Mojarra 2.1.17
> -------------------------
>
>                 Key: RF-12712
>                 URL: https://issues.jboss.org/browse/RF-12712
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: regression
>    Affects Versions: 4.3.0.CR1
>            Reporter: Jan Papousek
>            Assignee: Lukáš Fryč
>            Priority: Blocker
>             Fix For: 4.3.0.CR1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> While testing Metamer 4.3.0.CR1, I found some issues caused by Mojarra 2.1.16. Here is an example:
> # deploy Metamer (tomcat7-mojarra classifier) to Tomcat 7
> # open http://localhost:8080/metamer-mojarra/faces/components/richDataGrid/scroller.xhtml
> # set @elements attribute to 5
> # go to the second page (in data scroller) -> it resets @elements value

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira