We have WS deployed on jboss-4.2.2 using JBOss ws2.01 and client is running in .NET and during out testing we started getting same exception. On further analysis we found out that issue was on .NET code and not our WS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133345#4133345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133345 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
