Overriding the soapheader Namespace

[Michael Peters]

I wish to change/set the namespace for a header in my web service. I have
found the following code and it does not appear to work and my assumption is
because I am using RPC encoding...

[WebService(Namespace="http://www.mydomain.net/ns")]
public class Service1 : System.Web.Services.WebService
{
// ...

[XmlElement(Namespace="http://www.myotherdomain.net/headers")]
public MyHeader timeHeader;

[WebMethod]
[SoapHeader("timeHeader",Direction=SoapHeaderDirect ion.InOut)]
//...

Is there something I should use instead of the XmlElement to override the
header's namespace?

TIA

[Steven Cheng[MSFT]]

Hi Michael,

Welcome to the MSDN newsgroup.

As for the ASP.NET webservice's SoapHeader element namespace problem, it is
the expected behavior because the SOAP Rpc encoded message format won't
generate the SOAP message according to the WSDL xml schema or the .NET
class's xml seriazliation format. RPC style SOAP message will generate xml
content for a certain object structure following the encoding rules

#5.1 Rules for Encoding Types in XML
http://www.w3.org/TR/2000/NOTE-SOAP-...#_Toc478383513

So in order to make our web service's request/response SOAP message (XML
content) conforms to our XML schema or .NET class's xml serialization
defination, we should use Document/Literal message style instead of
RPC/encoded....

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Michael Peters]

So to clarify...there is no way for me to override/set the namespace for the
timeHeader structure below.
[WebService(Namespace="http://www.mydomain.net/ns")]
public class Service1 : System.Web.Services.WebService
{
// ...

[XmlElement(Namespace="http://www.myotherdomain.net/headers")]
public MyHeader timeHeader;

[WebMethod]
[SoapHeader("timeHeader",Direction=SoapHeaderDirect ion.InOut)]
//...
"Steven Cheng[MSFT]" <st*****@online.microsoft.com> wrote in message
news:4P**************@TK2MSFTNGXA02.phx.gbl...

Hi Michael,

Welcome to the MSDN newsgroup.

As for the ASP.NET webservice's SoapHeader element namespace problem, it
is
the expected behavior because the SOAP Rpc encoded message format won't
generate the SOAP message according to the WSDL xml schema or the .NET
class's xml seriazliation format. RPC style SOAP message will generate xml
content for a certain object structure following the encoding rules

#5.1 Rules for Encoding Types in XML
http://www.w3.org/TR/2000/NOTE-SOAP-...#_Toc478383513

So in order to make our web service's request/response SOAP message (XML
content) conforms to our XML schema or .NET class's xml serialization
defination, we should use Document/Literal message style instead of
RPC/encoded....

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Steven Cheng[MSFT]]

Thanks for your respone Michael,

Yes, for RPC style message, the soap header's element namespace is an
autogenerated encoding namespace, which derived from the service's
namespace but do not utilize the XML Element's namespace... So those XML
Serizliation attribute can not control that.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Michael Peters]

OK...here's a WSDL for a test webservice. It appears to be
Document/Literal. I also have the following line of code and it does not
appear to modify the WSDL. Can you tell me why?

[WebService(Namespace="http://Com.SouthernCompany.SecurityTest/webservices/")]
public class Service1 : System.Web.Services.WebService

{

[XmlElement(Namespace="https://ws.southernco.com/CoolSecurity")]

public Com.SouthernCompany.Cool.Security.ScCredentials
authenticationCredentials;

<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://Com.SouthernCompany.SecurityTest/webservices/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
targetNamespace="http://Com.SouthernCompany.SecurityTest/webservices/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
+ <s:schema elementFormDefault="qualified"
targetNamespace="http://Com.SouthernCompany.SecurityTest/webservices/">
- <s:element name="HelloWorld">
<s:complexType />
</s:element>
- <s:element name="HelloWorldResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="HelloWorldResult"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ScCredentials" type="tns:ScCredentials" />
- <s:complexType name="ScCredentials">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DirectUserNameToken"
type="tns:ScUserNameToken" />
<s:element minOccurs="0" maxOccurs="1" name="OriginatingUserNameToken"
type="tns:ScUserNameToken" />
<s:element minOccurs="0" maxOccurs="1" name="Created" type="s:string" />
</s:sequence>
</s:complexType>
- <s:complexType name="ScUserNameToken">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="UserName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Type" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Nonce" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="BinarySecurityToken"
type="tns:ScBinarySecurityToken" />
</s:sequence>
</s:complexType>
- <s:complexType name="ScBinarySecurityToken">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ID" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="ValueType" type="s:string" />
</s:sequence>
</s:complexType>
</s:schema>
</wsdl:types>
- <wsdl:message name="HelloWorldSoapIn">
<wsdl:part name="parameters" element="tns:HelloWorld" />
</wsdl:message>
- <wsdl:message name="HelloWorldSoapOut">
<wsdl:part name="parameters" element="tns:HelloWorldResponse" />
</wsdl:message>
- <wsdl:message name="HelloWorldScCredentials">
<wsdl:part name="ScCredentials" element="tns:ScCredentials" />
</wsdl:message>
- <wsdl:portType name="Service1Soap">
- <wsdl:operation name="HelloWorld">
<wsdl:input message="tns:HelloWorldSoapIn" />
<wsdl:output message="tns:HelloWorldSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="Service1Soap" type="tns:Service1Soap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document" />
- <wsdl:operation name="HelloWorld">
<soap:operation
soapAction="http://Com.SouthernCompany.SecurityTest/webservices/HelloWorld"
style="document" />
- <wsdl:input>
<soap:body use="literal" />
<soap:header message="tns:HelloWorldScCredentials" part="ScCredentials"
use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
<soap:header message="tns:HelloWorldScCredentials" part="ScCredentials"
use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="Service1">
- <wsdl:port name="Service1Soap" binding="tns:Service1Soap">
<soap:address
location="http://localhost/WebServiceSecurityTest2/Service1.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
"Steven Cheng[MSFT]" <st*****@online.microsoft.com> wrote in message
news:IQ**************@TK2MSFTNGXA02.phx.gbl...

Thanks for your respone Michael,

Yes, for RPC style message, the soap header's element namespace is an
autogenerated encoding namespace, which derived from the service's
namespace but do not utilize the XML Element's namespace... So those XML
Serizliation attribute can not control that.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Michael Peters]

I simply wish to override the namespace for the ScCredentials structure

Thank you,
MP

"Steven Cheng[MSFT]" <st*****@online.microsoft.com> wrote in message
news:IQ**************@TK2MSFTNGXA02.phx.gbl...

Thanks for your respone Michael,

Yes, for RPC style message, the soap header's element namespace is an
autogenerated encoding namespace, which derived from the service's
namespace but do not utilize the XML Element's namespace... So those XML
Serizliation attribute can not control that.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Michael Peters]

And just incase you need it....here's the declaration for the method using
the SoapHeader..
[WebMethod]

[System.Web.Services.Protocols.SoapHeader("authenti cationCredentials",
Direction=System.Web.Services.Protocols.SoapHeader Direction.InOut)]

public string HelloWorld( string test)

[Steven Cheng[MSFT]]

Hi Michael,

Have you tried directly apply namespace on the custom SoapHeader class
itself. like:

[XmlRoot("MySoapHeader",Namespace="http://mytest.dotnet.org")]
public class MyHeader : SoapHeader
{
...................

It works on my side.

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)