[
http://jira.jboss.com/jira/browse/RF-1923?page=comments#action_12404132 ]
Michael Youngstrom commented on RF-1923:
----------------------------------------
I noticed that in RichFaces 3.2 some of the state saving code was given back to the
implementation. If this portion of state saving was given back to the implementation as
well then you can close this issue.
Server-side state saving sensitive to model changes
---------------------------------------------------
Key: RF-1923
URL:
http://jira.jboss.com/jira/browse/RF-1923
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.1.3
Reporter: Michael Youngstrom
Assigned To: Nick Belaevski
Fix For: 3.2.1
Many frameworks such as Seam store Objects in the ViewRoot and expect those values to
function the same whether using server or client state saving. JSF and Myfaces both
provide an option to serialize view state before storing it in the Session. Since the
newly introduced AjaxStateManager overrides the implementation's state manager it
should provide a similar option.
See the following JSF-RI issue for more context:
https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=632
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira