Thanks for presenting your solution to a similar problem. We share the hope for
attention of the Seam team to these conversation switching issues. In your
case, the new conversation only starts after the redirect, in the next request.
That makes a big difference. I need to switch to another
Thanks for the input. It is what i was looking for.
However, it is strange that there is no direct support for this... I was
wondering if using one big top level conversation then nested conversations
couldn't do the job (i am a noob, remember :) ?
In fact, my problem is to manage workspace a
Folks,
We faced a similar situation a few days ago. The user could click on a
hyperlink in a page to go to a different page which was required to open in a
new non-nested conversation. Before redirecting to the new page, the
application was required to process the edits the user had made on
Hi
I have a similar problem and i am quite new to Seam. Has anyone a solution ?
marcelkolsteren could you please explain how you did it using the API ?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129460#4129460
Reply to the post :
Good to know that I'm not the only one who needs this functionality. I posted
my solution for switching to another long running conversation on my weblog:
http://marcelkolsteren.blogspot.com.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129479#4129479
Reply
Leaving the long-running conversation programatically in the action method
turns out to be no solution: Seam's ConversationInterceptor throws an
IllegalStateException before the method is executed, because the @Begin
annotation doesn't specify join=true. I could try to work around this by
