Thanks Geoff. I posted this also to the richfaces list: http://jboss.com/index.html?module=bb&op=viewtopic&t=131586 There is also an issue in their jira: http://jira.jboss.com/jira/browse/RF-1519
Michael -----Original Message----- From: Geoff Longo [mailto:[EMAIL PROTECTED] Sent: Montag, 10. März 2008 20:37 To: MyFaces Discussion Subject: Re: t:saveState and richfaces ? I think this might have been addressed in the latest RichFaces development builds (3.2?) but I haven't been able to confirm. Has anybody gotten around this issue? On Mon, Mar 10, 2008 at 1:39 PM, Michael Heinen <[EMAIL PROTECTED]> wrote: > > > > > I am facing a problem with t:saveState which could be caused by > richfaces/ajax4jsf (but not sure about it) > > The saved component is still "living" after leaving and revisiting a page. > > > > I defined a managed bean in request scope: > > <managed-bean-name>WorkflowController</managed-bean-name> > > <managed-bean-scope>request</managed-bean-scope> > > > > It is saved via: > > <t:saveState id="savedWorkflowController" value="#{WorkflowController}"/> > > > > If I enter the page the first time then the Constructor of > WorkflowController is called. If I now leave the page and re-enter it I > expect that a new instance is created, but it isn't. > > > > I am sure that this feature was working well in the past. > > An older version of my workspace with ajax4js4 1.1.0 is running fine. > Unfortunately I can't go back to this version in my current workspace due to > incompatibilities. > > > > Any ideas how to isolate this problem quickly? > > > > My enviroment: > > myFaces 1.1.5 > > tomahawk 1.1.5 snapshot > > richfaces-ui-3.1.4 GA > > tiles and jsps (no facelets) > > server-side state saving > >
