Gavin,<br><br>Since you reached an interlude (however brief it may be), I&#39;d like to take the opportunity to reconsider the conversation context lifecycle. Currently, the spec states:<br><br>- For a JSF faces request, the context is active from the beginning of the apply request values phase until the response is complete.<br>
- For a JSF non-faces request, the context is active during the render response phase.<br><br>I feel that these boundaries are two narrow. I&#39;ll focus first on the faces request. In Seam, it&#39;s necessary to delay resuming the conversation until the apply request values phase because the conversation id is stored in the view root. At one time, the conversation context was even stored in the view root, making it even more imperative. But we get a chance to start fresh.<br>
<br>There are three factors that call for the boundaries to be extended:<br><br>- As of JSF 2.0, parts of the component tree is visited in the restore view phase, which happens to resolve value expressions bound to UIData components. This triggers a scope not active exception if a conversation-scoped bean is hit.<br>
- JSF 2.0 gives us far greater flexibility to control inbound and outbound requests. So it&#39;s no longer necessary to store the id in the view root. The query string would be sufficient (I&#39;ve already modified Web Beans to prototype this)<br clear="all">
- Servlets on subsequent requests may want to participate in the conversation (and perhaps even servlet filters)<br><br>For all of these reasons, I&#39;d like the conversation lifecycle to wrap the entire JSF lifecycle and i&#39;d like the conversation id to be propagated using a query string parameter since that&#39;s the most universal way of propagating state. As a result, custom servlets can read this value and restore the conversation as needed. It&#39;s really inconvenient for the conversation id to be hidden away into the component tree, aside from being problematic in JSF 2.0.<br>
<br>Please reconsider. Thanks.<br><br>-Dan<br><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don&#39;t hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters.  Please don&#39;t hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>