I have a service which adds SOAP headers to its response by adding them directly to the SOAPEnvelope object which is, itself, retrieved from the MessageContext. The headers show up perfectly when I view them in the SOAP Monitor. My problem is that I need to be able to read the headers in a .NET client.

Near as I can tell, the only way to make .NET aware of the headers is to define them in my WSDL. But the auto-generated WSDL of Axis does not include the headers, and I really do not want to use manually written WSDLs. So:

Is there some way in my service to add the headers in such a way that Axis is aware of them and includes them in the auto-generated WSDL?

If not, is there some way to extend the ?wsdl autogen process so that I could manually include the header info but autogen the rest? I know how to make ?wsdl spit out a pre-made file, but I would still like it to do most of the heavy lifting on its own, if possible.

If not, does anyone know of a way to get to the SOAP headers or even the raw SOAP message itself in .NET so that I don't have to rely on WSDL definitions to find my headers?

Cheers,
-Josh Emmons



Reply via email to