It is a general design desission that we made. JBossWS won't consume illegal SOAP messages from SOAP stack X.
Axis has been more lenient WRT that, but recent interop tests actually check for strict behaviour. With the current implementation, the message would have to be fixed out of scope. i.e. by some FixIllegalSOAPMessageFilter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942456#3942456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942456 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
