-
1. Re: nested conversation with explicit id
gavin.king Feb 14, 2007 6:33 PM (in response to ebu)If so, add an issue to JIRA and I'll take a quick look at that.
-
-
3. Re: nested conversation with explicit id
ebu Mar 5, 2007 4:52 PM (in response to ebu)Hi,
If i understand correctly it's impossible to swith to the old conversation if there is long running one:class ConversationInterceptor ... public boolean redirectToExistingConversation(Method method) { if ( !Manager.instance().isLongRunningConversation() ) { ...
is it correct? And if so, what is idea behind it?
wbr, eugen. -
4. Re: nested conversation with explicit id
ebu Mar 6, 2007 4:59 AM (in response to ebu)I would really appreciate any help!
wbr, eugen. -
5. Re: nested conversation with explicit id
raffaele.camanzo Mar 6, 2007 9:36 AM (in response to ebu)Hi Eugen,
I did not try with nested conversation but I don't see any counter-indication (and I hope that there are not), anyway, if you need to switch to a conversation with a given id (or known, this is necessary for this mechanism) you can try to do this:Manager.instance().switchConversation(<conversationIdToSwitchTo>);
Hope this will be useful for you.
Regards,
Raffaele Camanzo -
6. Re: nested conversation with explicit id
raffaele.camanzo Mar 6, 2007 10:36 AM (in response to ebu)I forgot an important note: I tried to do this from a long running conversation and Seam switches from one long running to the other long running conversation without any problem.
Regards,
Raffaele Camanzo -
7. Re: nested conversation with explicit id
ebu Mar 6, 2007 1:39 PM (in response to ebu)Hi,
Thank you for help. Yes it works, but as pointed by Gavin (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102935, last post on the page) usage of Manager is discouraged, and besides all that api calls from the app code makes it cluttered and thus spoils most of seam's beauty.
wbr, eugen. -
8. Re: nested conversation with explicit id
ebu Mar 6, 2007 7:01 PM (in response to ebu)So, is there any way to annotate a method with @Begin so that it will nest conversation if no conv. with given id exists and pick up existing one if it's available?
Something like this:@Begin(nested="true", id="update#{item.id}" public void editItem(){ }
Actually, i don't need those "update" conversations to be nested, it would be sufficient to have them 'concurrent', i.e. isolated, without access to parent variables and so on.
wbr, eugen.