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
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
In my application I have an action method that needs to leave (not end) the
current long running conversation, and start a new one. I tried the following
options:
| * annotate the method with @Begin = that doesn't work, because it
requires that the current conversation is not long running;
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
I encountered the same problem in my J2EE application, which uses Seam
2.0.0.GA. It is caused by a bug in JBoss/Seam. See the JIRA issues JBSEAM-2214
and JBSEAM-2224. I got rid of the problem by installing the fix
(EntityBeanList.java version 1.6).
View the original post :
The timeout specified in jboss.xml is only used if the EJB3 container needs to
create a new transaction when the method in the session bean is called. A new
transaction is only created in the following two cases:
- the transaction attribute is Required and there is no transaction running
- the
