axis-1.1.jar is not ok. JBossWS uses a modified version of axis-1.1 that adds J2EE specific functionality to axis, like BasicProfile-1.0 complientcy. The jboss-ws4ee.sar contains the axis-ws4ee.jar. That is the only valid axis version to be used with JBossWS.
Turn on axis debug level on the client side. Make sure the headers are put in the soap message. If not, check if the ClientLoginHandler is executed as part of client side axis handler chain. If you see the headers in the message make sure the ServerLoginHandler is excuted on the server side, it should set the principal/credential in the SecurityAssociation. See webservice/samples/server-sec in jboss-head for a working implementation. The sample is not yet ported to the jboss-4.0 branch. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851166#3851166 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851166 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
