ok, it looks like I have found a workaround for this: It looks like if you wrap the call into a batch:
| Seam.Remoting.startBatch(); | remoteManager.sendAnswer(..,...); | Seam.Remoting.executeBatch(); | the conversation is propagated and the SSB is retrieved. So, until this issue is fixed, wrapping calls into a batch, even if you only have one call to make, does the trick. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011434#4011434 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011434 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
