[richfaces-issues] [JBoss JIRA] Reopened: (RF-8204) AjaxStateManager: view id sequence is increased for AJAX requests under JSF 2.0

[Pavol Pitonak (JIRA)]

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

Pavol Pitonak reopened RF-8204:
-------------------------------



Recently I created a test case (https://jira.jboss.org/jira/browse/RFPL-300) that verifies this bug. It works fine with JBoss 5.1.0.GA, but not with Tomcat 6, see https://jira.jboss.org/jira/browse/RFPL-317.

In Tomcat, values in all forms change after both ajax and non-ajax requests (tested with 3.3.3.BETA1 and 3.3.3-SNAPSHOT).

> AjaxStateManager: view id sequence is increased for AJAX requests under JSF 2.0
> -------------------------------------------------------------------------------
>
>                 Key: RF-8204
>                 URL: https://jira.jboss.org/jira/browse/RF-8204
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core, JSF 2.0, performance
>    Affects Versions: 3.3.3.BETA1
>            Reporter: Nick Belaevski
>            Assignee: Nick Belaevski
>            Priority: Critical
>             Fix For: 3.3.3.BETA1
>
>
> In JSF 1.2.x ResponseStateManager had the only responsibility of reading/writing state according to rendering technology used.
> In Sun RI JSF 2.0 ResponseStateManager also has the responsibility of actually storing state in session (the same functionality as implemented in RF AjaxStateManager), that's why it assigns new views sequence number for AJAX requests. MyFaces 2.0 implements this functionality the same as in JSF 1.2 

-- 
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