openwebbeans-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sven Linstaedt <>
Subject Re: Starting long running conversations
Date Wed, 11 Nov 2009 16:30:52 GMT
Hi Mark,

I agree with you that this should not be part of the spec. I took a brief
look at the number guess example. In this application the conversation is
started during a postback action event. This implies the "calling" page
knows about the fact, the upcoming page needs an long running conversation,
which is not the behavior I am looking for.

Anyhow I have not understand your last sentence at all. I believe instead of
CDI (context and dependency injection?) you mean CID, which is managed by

My current plan is writing a FaceletHandler, which is used in the view's
metadata block to annotate this view for requiring a long runnung
conversation. For this task I have to lookup the current conversation
(likely) from the BeanManager, which in turn needs to be looked up too. Do
you know if there is any way to lookup the BeanManager from outside of CDI
other than trough JNDI's java:comp/BeanManager?

br, Sven

2009/11/11 Mark Struberg <>

> Hi Sven!
> JSR-299 doesn't define any such UI mechanisms like SEAM or Springs
> @Controllers.
> But it would be pretty easy to implement those, e.g. in the guess sample.
> It should imho not be part of the core though.
> As a small tip: We already have an OWB-internal SPI for conversation
> handling and James and I managed to implement conversations for Wicket UIs.
> The basic question is where to store something like the CDI of the
> FacesContext in the renderes html.
> LieGrue,
> strub
> *Von:* Sven Linstaedt <>
> *An:*
> *Gesendet:* Mittwoch, den 11. November 2009, 0:04:45 Uhr
> *Betreff:* Starting long running conversations
> Hi,
> because I am just fiddling around with long running (aka non transient)
> conversations, I would like to know, if someone has dealt with the problem
> of starting a long running conversation during a nonfaces (GET) request
> before.
> My current (not working) solution is, using a conversation scoped
> controller bean in the view, which get's instantiated during the render
> response phase and which set the conversation'S transient state in it's
> @PostConstruct method. Unfortunately OWB (have not tested weld yet) does
> it's "conversation.isTransient()" check before that phase, so the
> conversation's ID won't get populated to the view's attributes
> (org.apache.webbeans.jsf.WebBeansPhaseListener:170) and thus is not
> available on the next post back, resulting in a new conversation being
> started.
> From my experience with Seam I remember they used some kind of external xml
> configuration that maps URLs to action (like the traditional url controller
> frameworks like struts). I would not like to use a similar mechanism in my
> application, because I do not like xml files after all ;) so here is my
> question:
> What do you think is the best way to start a long running conversation from
> a GET request?
> br, Sven

View raw message