Author: manaRH Date: 2008-11-03 03:35:03 -0500 (Mon, 03 Nov 2008) New Revision: 9478 Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml Log: JBPAPP-1309 Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml =================================================================== --- branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml 2008-10-31 19:47:18 UTC (rev 9477) +++ branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml 2008-11-03 08:35:03 UTC (rev 9478) @@ -47,6 +47,24 @@ <programlisting role="XML"><![CDATA[<context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> +</context-param>]]></programlisting> + + <para> + There is a minor gray area in the JSF specification regarding the mutability of view state values. Since + Seam uses the JSF view state to back its PAGE scope this can become an issue in some cases. If you're + using server side state saving with the JSF-RI and you want a PAGE scoped bean to keep its exact value + for a given view of a page you will need to specify the following context-param. Otherwise if a user + uses the "back" button a PAGE scoped component will have the latest value if it has changed not the + value of the "back" page. (see + <ulink url="https://javaserverfaces-spec-public.dev.java.net/issues/show_bu... + Spec Issue + </ulink> + ). This setting is not enabled by default because of the performance hit of serializing the JSF view + with every request. + </para> + <programlisting role="XML"><![CDATA[<context-param> + <param-name>com.sun.faces.serializeServerState</param-name> + <param-value>true</param-value> </context-param>]]></programlisting> </sect2>