]
Pavol Pitonak commented on RF-8204:
-----------------------------------
The test case tests three forms that are in richfaces-demo in State Manager API page.
First it performs an ajax-request and verifies that values did not change. Then it perform
a non-ajax request and verifies that values did change. In both cases it verifies that all
three values on the mentioned page are equal.
For further info see test's source:
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: