Conversation Scope in non-JSF environment...

[James Carman <ja...@carmanconsulting.com>]

Should I be able to mark my beans as @ConversationScoped in a non-JSF
environment?

Re: Conversation Scope in non-JSF environment...

[James Carman <jc...@carmanconsulting.com>]

On Tue, Mar 24, 2009 at 1:05 AM, Gurkan Erdogdu <gu...@yahoo.com> wrote:
> Conversation Scope heavily depends on the JSF lifecycle in the
> specification. So much of the magic occurs inside the JSF
> WebBeansPhaseListener class. And as Mark said, there is a filter to
> intercepts request for conversation related stuff.
>
> Maybe it is possible to write generic conversation scoped context but I have
> not thought so far.
>
> Its great you help out on this :)

I would love to help out!  I got the specification printed today (I
hate reading online), so I'll look into this more thoroughly when I
receive my copy.  I just need to wrap my head around what a
conversation actually "is" per the specification.

I notice that you guys do some work in that filter that appends a
"cid" parameter to the redirected URL.  The only problem with that is
that it could conflict with the application's parameters, right?

Re: Conversation Scope in non-JSF environment...

[Gurkan Erdogdu <gu...@yahoo.com>]

Hi James;

Conversation Scope heavily depends on the JSF lifecycle in the specification. So much of the magic occurs inside the JSF WebBeansPhaseListener class. And as Mark said, there is a filter to intercepts request for conversation related stuff.

Maybe it is possible to write generic conversation scoped context but I have not thought so far. 

Its great you help out on this :)

Thanks;




________________________________
From: James Carman <ja...@carmanconsulting.com>
To: openwebbeans-user@incubator.apache.org
Sent: Monday, March 23, 2009 10:01:36 PM
Subject: Conversation Scope in non-JSF environment...

Should I be able to mark my beans as @ConversationScoped in a non-JSF
environment?