Well, I was too confident in my last post: following your instruction, I clearly see in the logs that the generated SOAP message does not contain any header: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soapenv:Body soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> | <ns1:getContactInfo xmlns:ns1="http://ec.ep.dit.isp.tests/ws4ee"> | <in0 xsi:type="xsd:string">mafia</in0> | </ns1:getContactInfo> | </soapenv:Body> | </soapenv:Envelope> So I think that I have to follow your advice: anonymous wrote : If not, check if the ClientLoginHandler is executed as part of client side axis handler chain. though I do not know how to be sure of that. In the log, I can not find any entry coming from a class named "ClientLoginHandler".
Is there a specific configuration of Axis to use to achieve that? Thanks for your reply, David BTW. I looked at webservice/samples/server-sec and followed the test case to also ensure that the EJB responds correctly & can authenticate when called on his remote. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851417#3851417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851417 ------------------------------------------------------- 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
