STATE_SAVING_METHOD=server broken for ScopeType.CONVERSATION

[andrewa]

Seems that setting the jsf STATE_SAVING_METHOD to server in web.xml breaks CONVERSATION scoped components. ie:

<context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>server</param-value>
</context-param>

The symptom is that the conversation doesnt persist between requests.

Session scoped components work fine ie. they do persist between requests.

Tested with current cvs booking+noejb on jas403 and noejb on tomcat. To reproduce; setup web.xml as per above fragment and run through the demo.

Can anyone shed any light on this?

[gavin.king]

Right, this is a known limitation of using Seam with MyFaces, due to how MyFaces does server-side state saving (I'm not going to call it an actual *bug* in MyFaces, but it is suboptimal).

It looks like I have forgotten to document this critical thing! Oooop!

[gavin.king]

Now documented in CVS.

[elmosca2]

This has now been fixed in MyFaces and will be available in the next release!