Thank you for the answers. I've decided to step back and use JAX-WS 2.0, hopefully integration with external parties won't be a problem. "alessio.soldano(a)jboss.com" wrote : I'd need to double check what was available in AS 4.2.2, I think the -t 2.1 option was later disabled because the implementation of JAX-WS 2.1 was not complete yet. I am sure I used the "-t 2.1" switch on default install of AS 4.2.2.GA. "alessio.soldano(a)jboss.com" wrote : For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as the JAX-WS 2.1 has been completed there. | Otherwise (if you cant move to AS 4.2.3 which is the oldest target container supported by JBossWS 3.1.0) try with JBossWS-Metro 3.0.5, which already had full JAX-WS 2.1 impl. I'll probably have to stay with 4.2.2 now, but I'll take the information about working WS 3.1.0 and JAX-WS 2.1 into accound when I'll be considering AS upgrade. The Metro stack was giving me some problems after deployment, I briefly went through the exceptions' stacks but had no time to figure out what exactly went wrong. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227464#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...