"pete.muir(a)jboss.org" wrote : Wrap your calls to Seam components in an ContextHttpServletRequest. Make sure the conversationId is in the request parameter map you pass in. Can I put the conversation id into the JSON Message and, in that case, do the same logic as in "SOAPRequestHandler" then without wrapping my code in ContextHttpServletRequest which need the request param ? What SOAPRequestHandler does for each request is : | | ServletLifecycle.beginRequest(request); | | ServletContexts.instance().setRequest(request); | | String conversationId = //I extract my cid here | ConversationPropagation.instance().setConversationId( conversationId ); | Manager.instance().restoreConversation(); | | ServletLifecycle.resumeConversation(request); and after the request completion : | String conversationId = Manager.instance().getCurrentConversationId(); | if (conversationId != null) | { | //put the cid in my JSON response | } | Manager.instance().endRequest( new ServletRequestSessionMap(request) ); Is that enough to use the Seam-managed persistence context and Seam managed transaction ? Tks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116056#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...