Nevermind, it looks like Trinidad 1.2.6 is no longer compatible with facelets
https://issues.apache.org/jira/browse/TRINIDAD-955 Looks like I will have to use 1.2.5 -Andrew On Wed, Feb 20, 2008 at 7:34 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > Removing the CLIENT_STATE_METHOD and CACHE_VIEW_ROOT parameters > doesn't help. This gets: > > Caused by: java.lang.ClassCastException: [Ljava.lang.Object; cannot be > cast to java.lang.String > at > org.apache.myfaces.trinidadinternal.util.SubKeyMap._getBaseKey(SubKeyMap.java:116) > at > org.apache.myfaces.trinidadinternal.util.SubKeyMap.get(SubKeyMap.java:75) > at > org.apache.myfaces.trinidadinternal.application.StateManagerImpl.restoreView(StateManagerImpl.java:526) > at > com.sun.faces.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:290) > at > org.jboss.seam.jsf.SeamViewHandler.restoreView(SeamViewHandler.java:93) > at > org.jenia.faces.template.handler.ViewHandler.restoreView(ViewHandler.java:263) > at > com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:316) > at > javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:193) > at > org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:260) > at > com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:141) > > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) > at > com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > ... 43 more > > > > > On Wed, Feb 20, 2008 at 7:28 PM, Andrew Robinson > <[EMAIL PROTECTED]> wrote: > > After upgrading from 1.0.5 to 1.2.6 I am having my PPR fail. I keep > > jetty expired view errors: > > > > Caused by: javax.faces.application.ViewExpiredException: > > viewId:/test.jsf - View /test.jsf could not be restored. > > at > com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:187) > > at > com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) > > at > com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > > > > I have full client side state: > > <context-param> > > > <param-name>org.apache.myfaces.trinidad.CLIENT_STATE_METHOD</param-name> > > <param-value>all</param-value> > > </context-param> > > <context-param> > > <param-name>org.apache.myfaces.trinidad.CACHE_VIEW_ROOT</param-name> > > <param-value>false</param-value> > > </context-param> > > <context-param> > > > <param-name>org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE</param-name> > > <param-value>false</param-value> > > </context-param> > > <context-param> > > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > > <param-value>client</param-value> > > </context-param> > > > > I am seeing the viewState being sent back in the AJAX request. > > > > I did a forum search and came up empty. Is there a problem with true > > client side state in 1.2.6? > > > > BTW - I am using client side state as I plan to host on a server that > > won't have a very large heap so I want to conserve memory. > > > > -Andrew > > >
