Shane, Thanks for your reply, I'll give the new build a go. As for the session ID, I've been trying to add a cookie to a client generated by the JBossWS 2.0.0.GA wsconsume tool without any luck. As far as I understand session support in the client, it looks like you can instruct the client to participate in a session which it creates and manages itself. I was able to do this and get the resulting JSESSIONID cookie from the WS call. However I've not yet found a way to make a WS participate in an existing session (i.e. set my own JSESSIONID Cookie header). I believe there are some issues with session management in the 2.0.0 release. In particular, a session may be created but appears to get lost during subsequent requests. My prefered approach would have been to add the JSESSIONID myself rather than letting the client handle it, that way I can have servlets/web services/you name it all part of the same session. I'd also posted on the JBossWS regarding session management however I've yet to receive a reply: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112660 I've had an equally tough time adding a SOAP header from a JAX-WS 2.0 client runtime (JDK 6) in order to specify the conversation ID. Under JAX-WS 2.1 it looks very straight forward, but I've not found a portable solution for JAX-WS 2.0. I'm probably missing something obvious, but variations in standards and versions and even behaviour between vendors has just left me completely confused and bewildered. What clients have you guys been using for your testing? Cheers, Chris. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069143#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...