9 Replies Latest reply on Feb 26, 2009 3:44 PM by sri reddy

    tomahawk saveState not working with richfaces 3.1.4 (rf-1519

    Michael Heinen Newbie

      I am facing a problem with tomahawk t:saveState which seems to be caused by richfaces. The saved component is still "living" after leaving and revisiting a page.

      Pls see also jira issue rf 1519 http://jira.jboss.com/jira/browse/RF-1519

      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.

      My enviroment:
      myFaces 1.1.5
      tomahawk 1.1.5 snapshot
      richfaces 3.1.4 GA
      tiles and jsps (no facelets)
      server-side state saving

      What is the status of rf-1519 ?
      Will this be fixed in 3.1.5?
      Unfortunately I can't update to 3.1.2 because I have to use jsf 1.1