[seam-issues] [JBoss JIRA] (JBSEAM-3136) Consider Remvoing Client State Saving Suggestion

Marek Novotny (JIRA) issues at jboss.org
Wed Apr 2 07:09:12 EDT 2014

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

Marek Novotny closed JBSEAM-3136.

         Assignee: Marek Novotny
    Fix Version/s: 2.3.2.CR1
       Resolution: Done

recommendation was removed  
> Consider Remvoing Client State Saving Suggestion
> ------------------------------------------------
>                 Key: JBSEAM-3136
>                 URL: https://issues.jboss.org/browse/JBSEAM-3136
>             Project: Seam 2
>          Issue Type: Task
>          Components: Documentation Issues
>    Affects Versions: 2.0.2.GA
>            Reporter: Steve Roy
>            Assignee: Marek Novotny
>             Fix For: 2.3.2.CR1
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the seam-issues mailing list