I wasn't able to reproduce the problem since the attached deployment was referencing a WSDL file that wasn't present. However, I noticed that the jbossws jars are included in the ear file. this could lead to issues and possible conflicts. Can you try pulling the jboss jars out of the deployment, and just relying on the ones in container? If they aren't available copy the few that are missing into the server/lib directory.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024511#4024511
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024511
Which branch do we commit to for JBossWS 1.2.1 fixes? Is everything
going to go into trunk or is there going to be a separate branch again?
Regards,
Darran Lofthouse.