Re: [webbeans-dev] conversation context lifecycle
On Fri, May 29, 2009 at 2:40 PM, Clint Popetz <cpopetz(a)gmail.com> wrote:
My $.02 is that conversation propagation doesn't belong in the
spec. It's
very easy with the new SPI to set up the conversation context based on your
own rules, and this could be done to support servlets interoperating with
conversations that are started by JSF. I'd rather a named request parameter
wasn't in the spec. For example, that's not how Wicket will
activate/deactivate conversations, nor would anything else that used RESTful
notation for path processing (i.e. the conversation id looks like
/conversationId/3)
Right, I think the point about wicket is a very strong point. I still
think we should provide conversations for JSF OOTB, but servlets seems
much more debatable. At least, there would need to be some way to turn
it off.
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org