Further tests show that the problem does not appear when the bean that starts the nested
conversation is in the session scope. The problem occurs only when the bean is in the
conversation scope.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093355#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...