I guess this is a bug since if I use jbossws-1.2.0.SP1 I do not get this error. The jira
bug on this is still open so I guess I'll just use 1.2.0 until it is resolved.
If this isn't a bug, though, someone please let me know:)
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045598#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...