Consider Remvoing Client State Saving Suggestion
------------------------------------------------
Key: JBSEAM-3136
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3136
Project: Seam
Issue Type: Task
Components: Documentation Issues
Affects Versions: 2.0.2.GA
Reporter: Steve Roy
The Reference Guide has the following information:
Some JSF implementations have a broken implementation of server-side state saving that
interferes with Seam's conversation propagation. If you have problems with
conversation
propagation during form submissions, try switching to client-side state saving. You'll
need this in
web.xml:
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
per the forum thread,
http://www.seamframework.org/Community/StateSavingMethod, this
information appears to be out of date.
Although we found no server-side state issues in our application, we found this statement
concerning with regard to our application since moving to client state changed the size of
some rendered pages significantly.
It may be helpful to remove this out of date information to reduce confusion.
--
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