The release notes for jboss-jaxws_2.0.0GA indicate that this has been fixed. However,
I'm deploying with jboss-jaxws_2.0.1GA and I'm still getting the same exception.
Wasn't this fixed? If so, how? Do I need to do anything else?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096720#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...