But it doesn't expose these headers are part of the method signature. You're left to call setHeader yourself (and therefore have to manualy copy over the element names & namespaces from the WSDL, which is error prone). I think I logged a bug for this a while back.
Cheers Simon -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 7:35 AM To: [email protected] Subject: Re: soap:headers and explicit service context If you set up the wsdl correctly, then the generated code has the addition java objects for the stuff in soap headers. -- dims On 8/23/05, Hans Planting (CWEU-USERS/CWNL) <[EMAIL PROTECTED]> wrote: > Hi there, > > Is there support planned for explicit soap headers as described in > JAX-RPC 1.1 chapter 11.2.2? > With explicit soap headers I'd expect Axis to append additional > parameters for soap:headers following the service endpoint defined > paramers in the remote method signature. Also no custom > parsing/deserialization would need to be implemented. > Currently in order to process soap:headers you need to implement a > handler or use the setHeader and getHeader methods in > org.apache.axis.client.Stub and in both cases implement code to > parse/deserialize the soap elements; Axis does not deserialize the > contents of soap:headers to Java objects (correct me if I'm wrong - is > there a way to do this?). > > Thanx! > > Hans > -- Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
