I just encounterd this problem on JBoss 4.2.2 which includes an updated JBossWS. It seems
to only occur after an error in a previous deployment. Restarting the Application Server
seems to resolve the problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099324#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...