Don't worry; I think I've figured this out.
I had assumed that an object needed to be passed to the method in the generated stub. The actual web service implementation doesn't need a parameter but the generated stub method takes an object. I'm new to this but managed to find some reference to a Soap body element and decided to create one of these to pass in. This worked, so far as the web service call is concerned. However, it caused Axis to use messaging, rather than RPC. This, in turn, resulted in a response object that was a vector of SOAP body elements, which wasn't what was expected.
When I simply passed a null to the generated stub method it all worked wonderfully, since the object returned from the service call invoke method was the Java object I expected all along. I don't yet understand the detail of all this but it now works fine. I'm not sure why Sun's JWSDK handled this OK and Axis didn't but I'll leave that for another day.
Cheers,
Tony
- AW: AW: Session Management using SOAP Headers in AXIS Dorner Thomas
- Re: AW: AW: Session Management using SOAP Headers i... Mahen Perera
- Re: AW: AW: Session Management using SOAP Heade... Mahen Perera
- WSDL2Java and document/literal tony . q . weddle
- tony . q . weddle
