No, I have not tried adding debug tracing, but I did add a soap message hander to the service so I could see the inbound soap message. The message no longer contained any security information in the soap header as it previously did when using Axis. The classes that get used on the client side to generate the request soap message are different with JBossWS, so is it possible that this piece, implementing stub._setProperty(String,String), may not have been tested with JBossWS. I know for sure that when using the Axis ws4ee-client classes, when you call stub._setProperty(String,String), it added security related information to the soap header. I just can't seem to get this to happen with JBossWS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939991#3939991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939991 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
