1 Reply Latest reply on Dec 12, 2012 10:56 AM by Marek Schmidt

    Conversation id not restored from page context  / Seam 2.3.1  / javax.faces.PARTIAL_STATE_SAVING

    Peter Fry Newbie

      I am in the process of migrating a Seam 2.2.2.Final based application to Seam 2.3 (we run on JBoss 7.1.0.Final) .

       

      I am hitting

       

      https://issues.jboss.org/browse/JBSEAM-4976

       

      Which is targeted for Seam 2.3.1.CR1 .

       

      How is this issue intended to be solved? Should we expect a requirement to upgrade the version of JSF used in JBoss to JSF 2.2, see

       

      http://stackoverflow.com/questions/10337015/should-partial-state-saving-be-set-to-false

       

      OR will the recommendation still be to switch the partial state saving method to false.

       

      If there will be a more comprehensive solution in Seam 2.3.1.CR1 is there any guide as to its release schedule?

       

      UPDATE: I have tried both the PARTIAL_STATE_SAVING parameter solution and the hidden field solution and neither work for a h:commandButton

       

      The only solution that works for me is using <s:conversationId/> within the h:commandButton tag. My only concern is whether this will propagate a Seam conversation when I don't want it to?

       

      Peter.