On Tue, 2007-12-11 at 08:37 -0800, Ryan Lubke wrote: > > > Dave-53 wrote: > > > > Hi Ryan, > > > > Thanks for help. In web.xml, we have > > > > <context-param> > > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > > <param-value>server</param-value> > > </context-param> > > > > <context-param> > > <param-name>org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION</param-name> > > <param-value>20</param-value> > > </context-param> > > > > <context-param> > > <param-name>org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</param-name> > > <param-value>true</param-value> > > </context-param> > > > > <context-param> > > <param-name>org.apache.myfaces.COMPRESS_STATE_IN_SESSION</param-name> > > <param-value>false</param-value> > > </context-param> > > > > These parameters are not changed for RI, I am wondering if I need to > > change or add some for RI. > > > > Yes, I use <t:saveState> to save request-scope bean data. > > The senarios: > > > > On window 1, click link A, execute action that changed request scope > > bean data Foo, the response was shown on Window 2. It worked well. > > > > Again on window 1, click link A, this step did not go through Invoke > > Application phase. > > > > It works for MyFaces. > > > > Thanks for any help. > > Dave > > > > > > Well, JBoss 4.2.2 uses JSF RI 1.2_04 P02. Try upgrading to 1.2_06 [1], and > set com.sun.faces.serializeServerState to true. > We added the option to serialize component state to the session in 1.2_05. > > [1] > https://javaserverfaces.dev.java.net/servlets/ProjectDocumentList?folderID=8346&expandFolder=8346&folderID=0 >
Serializing the state (1) saves server memory, and (2) avoids ugly surprises when an app is later clustered and suddenly it is realised that objects in the component tree are not serializable. Similarly for compressing the state, that just saves memory but should have no effect on the app behaviour. I cannot see what link there could be between either of these settings and the described symptoms. Cheers, Simon
