SoapHeaders added from within SoapExtension have 'tempuri' namespace

[Dave Buxbaum via .NET 247]

Hi,

I have a SoapExtension that adds a SoapHeader to all outboundmessage s. This works fine, but I don't see a way to control thenamespace of the emitted header. Here is what I'm doing:

I have created a subclass of SoapHeader ('MyHeader') and thisclass is in a defined namespace. I then create an instance ofthis class within my SoapExtension (also in a defined namespace)and add it to outbound messages using something like:SoapMessag e.Headers.add(m yHeader).

The soap messages coming out of my SoapExtension have the header,and they look like this:

<soap:Header><m yHeader soap:actor="myA ctor"xmlns="htt p://tempuri.org/">

I need to place 'myHeader' into a real namespace. Is thispossible from within my SoapExtension, and how? I'd like avoiddoing this via the DOM if possible (I'm lazy!).

Thanks much,
Dave

--------------------------------
From: Dave Buxbaum

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>bCa5SLVQaEy yB+OjM8Hd7w==</Id>

[Rafal Gwizdala]

Dave Buxbaum via .NET 247 wrote:

Hi,

I have a SoapExtension that adds a SoapHeader to all outbound messages. This works fine, but I don't see a way to control the namespace of the emitted header. Here is what I'm doing:

I have created a subclass of SoapHeader ('MyHeader') and this class is in a defined namespace. I then create an instance of this class within my SoapExtension (also in a defined namespace) and add it to outbound messages using something like: SoapMessage.Hea ders.add(myHead er).

The soap messages coming out of my SoapExtension have the header, and they look like this:

<soap:Header><m yHeader soap:actor="myA ctor" xmlns="http://tempuri.org/">

I need to place 'myHeader' into a real namespace. Is this possible from within my SoapExtension, and how? I'd like avoid doing this via the DOM if possible (I'm lazy!).

Thanks much,
Dave

--------------------------------
From: Dave Buxbaum

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>bCa5SLVQaEy yB+OjM8Hd7w==</Id>

Try using Xml serialization attributes on the custom header class (but I
did not test it, dont blame me if it doesn't work).

Regards
Rafal Gwizdala