Well, this issue is fixed in JBossWS 2.0.2 and release should be available at the end of this month. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091577#4091577 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091577