Hi I checked the algorithms related on MyFaces and everything seems to be ok. I fixed https://issues.apache.org/jira/browse/MYFACES-3105 too, but that one is not your case. In fact, there are some special junit cases that ensures state saving algorithm is symmetric, and other tests ensures ajax and normal request are saved/restored correctly.
Maybe your problem is not related with JSF, and it has to be with something about your servlet configuration or special setup. Note that JSF relies on servlet session mechanism to state saving. regards, Leonardo Uribe 2011/6/25 Leonardo Uribe <[email protected]>: > Hi > > There was some changes on state saving algorithm. All tests done passed, but > the previous algorithm was preserved too. It was found a bug on 2.0.6, so > the following is valid 2.0.7 / 2.1.1 . Add in your web.xml file the > following: > > <context-param> > > <param-name>org.apache.myfaces.HANDLE_STATE_CACHING_MECHANICS</param-name> > <param-value>false</param-value> > </context-param> > > and then on faces-config.xml > > <state-manager>org.apache.myfaces.application.jsp.JspStateManagerImpl</state-manager> > > This goes inside <application> section. In this way the previous algorithm > is used instead. If that works let us know, to try to reproduce it and fix > it on future MyFaces versions. > > regards, > > Leonardo > > 2011/6/25 Hamed Iravanchi <[email protected]> >> >> Hi, >> >> I'm getting ViewExpiredSession by clicking on any button in my pages after >> upgrading MyFaces 2.0.5 to 2.0.6. >> My pages have multiple forms, any button in any of them raises the same >> error. >> >> I'm using facelets version 1.1.6. >> >> I see some changes in the state caching on the change list of 2.0.6, and >> I'm >> not sure is it something that I'm doing wrong (and it worked by chance in >> 2.0.5) or there's some bug in 2.0.6. >> (I tried 2.0.7, and it has the same problem.) >> >> -Hamed > >
