I don't have a services.xml, and I don't have the manageTransportSession parameter in my axis2.xml.
But I am just running an axis2 client and my client seems to run ok without them. I am stuck trying to figure out how to manipulate the SOAP header in my client-side handler. The semantics for manipulating the SOAP header has changed between axis1 and axis2. I am having trouble finding documentation and sample code that manipulates the SOAP header obtained from a MessageContext. From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 8:43 PM To: [email protected] Subject: RE: How to add a SOAP header in an axis2 custom client-side handler? didn't see your config params axis2.xml <parameter name="manageTransportSession">?</parameter> services.xml <service name="MultiplyService" scope="?"> Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. ________________________________ Subject: How to add a SOAP header in an axis2 custom client-side handler? Date: Wed, 13 Aug 2008 18:26:36 -0400 From: [EMAIL PROTECTED] To: [email protected] I am trying to figure out how to add a SOAP header in my client-side handler. I have the following axis1 code, but need an axis2 equivalent: /*********************************************************************** * Processes the header of a request message. This method will add the * session header to the outgoing request. * * @param context the message context associated with the request **********************************************************************/ private void invokeRequest( MessageContext context ) throws AxisFault { Message msg = context.getRequestMessage(); if (msg == null) throw new AxisFault( "Message not in context." ); SOAPEnvelope env = msg.getSOAPEnvelope(); SessionHeaderType sessionHeader = WebServiceClientHelper.getThreadSessionHeader( ); SOAPHeaderElement header = new SOAPHeaderElement(HEADER_NS, HEADER_NAME, sessionHeader); env.addHeader(header); } The SessionHeaderType class was generated from a wsdl and contains session credentials. Any pointers to appropriate documentation on how to manipulate headers, or sample code, would be appreciated. ________________________________ Your PC, mobile phone, and online services work together like never before. See how Windows(r) fits your life <http://clk.atdmt.com/MRT/go/108587394/direct/01/>
