You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openwebbeans.apache.org by Matthias Wessendorf <ma...@apache.org> on 2009/04/16 10:40:43 UTC
Re: Conversation Scope in non-JSF environment...
On Mon, Mar 23, 2009 at 10:51 PM, Mark Struberg <st...@yahoo.de> wrote:
>
> Hi James!
>
> The conversation handling for JSF works with the servlet Filter WebBeansJSFFilter. This contains a few JSF specific hooks and retrieves information from the FacesContext. So this filter cannot be used in Wicket applications.
why a filter? Couldn't do an extra FacesContextFactory do the trick?
See here -> http://tinyurl.com/deu24m
>
> But I think the ConversationImpl and the ConversationManager should be reusable for Wicket also.
>
> @Gurkan, maybe we should move those 2 classes out from the jsf package to an own conversation package?
>
> The next step would be to write an own Filter for Wicket Applications similar to the WebBeansJSFFilter.
>
> LieGrue,
> strub
>
> --- James Carman <ja...@carmanconsulting.com> schrieb am Mo, 23.3.2009:
>
>> Von: James Carman <ja...@carmanconsulting.com>
>> Betreff: Conversation Scope in non-JSF environment...
>> An: openwebbeans-user@incubator.apache.org
>> Datum: Montag, 23. März 2009, 21:01
>> Should I be able to mark my beans as
>> @ConversationScoped in a non-JSF
>> environment?
>>
>
>
>
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: Conversation Scope in non-JSF environment...
Posted by James Carman <jc...@carmanconsulting.com>.
On Thu, Apr 16, 2009 at 6:33 AM, Matthias Wessendorf <ma...@apache.org> wrote:
> I asked, why a filter (for JSF). Sorry for kinda hijacking the thread :D
Ahhhh, didn't understand that you were only talking about why the
filter. Hijack away! :)
Re: Conversation Scope in non-JSF environment...
Posted by Matthias Wessendorf <ma...@apache.org>.
On Thu, Apr 16, 2009 at 12:01 PM, James Carman
<jc...@carmanconsulting.com> wrote:
> On Thu, Apr 16, 2009 at 4:40 AM, Matthias Wessendorf <ma...@apache.org> wrote:
>> On Mon, Mar 23, 2009 at 10:51 PM, Mark Struberg <st...@yahoo.de> wrote:
>>>
>>> Hi James!
>>>
>>> The conversation handling for JSF works with the servlet Filter WebBeansJSFFilter. This contains a few JSF specific hooks and retrieves information from the FacesContext. So this filter cannot be used in Wicket applications.
>>
>> why a filter? Couldn't do an extra FacesContextFactory do the trick?
>> See here -> http://tinyurl.com/deu24m
>
> How does something with the name "Faces" in it make this a non-JSF
> environment? :) Whatever we do, the faceyness (for the record, I just
> coined that phrase) should be completely removed.
<snip>
The conversation handling for JSF works with the servlet Filter
WebBeansJSFFilter
</snip>
I asked, why a filter (for JSF). Sorry for kinda hijacking the thread :D
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: Conversation Scope in non-JSF environment...
Posted by James Carman <jc...@carmanconsulting.com>.
On Thu, Apr 16, 2009 at 4:40 AM, Matthias Wessendorf <ma...@apache.org> wrote:
> On Mon, Mar 23, 2009 at 10:51 PM, Mark Struberg <st...@yahoo.de> wrote:
>>
>> Hi James!
>>
>> The conversation handling for JSF works with the servlet Filter WebBeansJSFFilter. This contains a few JSF specific hooks and retrieves information from the FacesContext. So this filter cannot be used in Wicket applications.
>
> why a filter? Couldn't do an extra FacesContextFactory do the trick?
> See here -> http://tinyurl.com/deu24m
How does something with the name "Faces" in it make this a non-JSF
environment? :) Whatever we do, the faceyness (for the record, I just
coined that phrase) should be completely removed.