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
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
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?
If that is the only concern, then maybe the conversation propagation tag might help?
The current "fix" is to add the conversation id in the SeamViewHandler, which indeed causes a problem of propagating a Seam conversation even if one does not want to...
|Retrieving data ...|