My understanding of the issue is that the WebServiceContext (or should I say it's creation) currently has a hard dependency on servlets and it is this dependency which is causing our problem. As we are not calling into jbossws via a servlet container we do not have servlet contexts etc. It would be much better if the InvocationContext supported the methods required by the WebServiceContext (such as user principals/roles) in a generic manner and therefore break any hard dependency with the container. The WebServiceContext could then defer its functionality to the InvocationContext. What I have still to understand is why this is not evident from your JMS support. Looking at the code would suggest that it would suffer the same issues as are displayed from invocations coming through the ESB. Is my understanding correct? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120862#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...