run wsdl2java on test\wsdl\header\header.wsdl and look at the generated code.
-- dims On 8/23/05, Hans Planting (CWEU-USERS/CWNL) <[EMAIL PROTECTED]> wrote: > Ok, but if I for example use 'getHeader' in org.apache.axis.client.Stub, > I get a SOAPHeaderElement - is there a way to deserialize this to a java > object (using BeanDeserializer etc) without having to write code to > parse the contents of the elements? > > Hans > > > > Davanum Srinivas wrote: > > >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
