Accessing Soap Header

[Debasish Pramanik]

Hi All,

I have added a SoapHeader in my websevice, which is exposed as a variable
from my webservice. Whenver I access the header form my client I see the
name of variable being changed to <VaribaleName>Value.

public class MyClass: System.Web.Services.WebService

{

public Header RequestHeader;

[WebMethod]

[SoapHeader("RequestHeader")]

public String Method1(ref String Data)

{

}

In the Client we access as follows

Header header = new Header();

MyClass m = new MyClass();

m.HeaderValue = header;

Why it suffixed the it with value or is this the right way to access it.
--
Regards,

Debasish Pramanik
Assetlink India.
Phone: [phone] (226)

[John Saunders]

"Debasish Pramanik" <de***************@Assetlink.comwrote in message
news:e3**************@TK2MSFTNGP02.phx.gbl...

Hi All,

I have added a SoapHeader in my websevice, which is exposed as a variable
from my webservice. Whenver I access the header form my client I see the
name of variable being changed to <VaribaleName>Value.

public class MyClass: System.Web.Services.WebService

{

public Header RequestHeader;

[WebMethod]

[SoapHeader("RequestHeader")]

public String Method1(ref String Data)

{

}

In the Client we access as follows

Header header = new Header();

MyClass m = new MyClass();

m.HeaderValue = header;

Why it suffixed the it with value or is this the right way to access it.

If it works, then why ask why?

John

[Debasish Pramanik]

Why can't I access it as RequestHeader of the Service Object ?????

--
Regards,

Debasish Pramanik
Assetlink India.
Phone: [phone] (226)

"John Saunders" <john.saunders at trizetto.comwrote in message
news:Ok**************@TK2MSFTNGP02.phx.gbl...

"Debasish Pramanik" <de***************@Assetlink.comwrote in message
news:e3**************@TK2MSFTNGP02.phx.gbl...

Hi All,

I have added a SoapHeader in my websevice, which is exposed as a

variable

from my webservice. Whenver I access the header form my client I see the
name of variable being changed to <VaribaleName>Value.

public class MyClass: System.Web.Services.WebService

{

public Header RequestHeader;

[WebMethod]

[SoapHeader("RequestHeader")]

public String Method1(ref String Data)

{

}

In the Client we access as follows

Header header = new Header();

MyClass m = new MyClass();

m.HeaderValue = header;

Why it suffixed the it with value or is this the right way to access it.

If it works, then why ask why?

John

[John Saunders]

"Debasish Pramanik" <de***************@Assetlink.comwrote in message
news:uB****************@TK2MSFTNGP03.phx.gbl...

Why can't I access it as RequestHeader of the Service Object ?????

Sorry, I didn't notice that you were confusing the client and the server.
The service object does not exist on the client. What's on the client (in
your case) is a proxy class generated from the WSDL file which .NET produced
from the metadata on the server. .NET chose to create a proxy class with a
Header object called HeaderValue. That's not within your control.

So, don't worry about the name difference, as MyClass on the client and
MyClass on the server are two classes with almost no relationship between
them.

In other words, just use what works, HeaderValue, and don't expect the
client and server to be the same thing.

John

[Debasish Pramanik]

Hi John,

Thanks for the reply !!

I have seen some site whee they say it depend upon the namespace that you
can provide the attribute that controls the name. Do you have any idea about
that.

--
Regards,

Debasish Pramanik
Assetlink India.
Phone: [phone] (226)

"John Saunders" <john.saunders at trizetto.comwrote in message
news:eI**************@TK2MSFTNGP06.phx.gbl...

"Debasish Pramanik" <de***************@Assetlink.comwrote in message
news:uB****************@TK2MSFTNGP03.phx.gbl...

Why can't I access it as RequestHeader of the Service Object ?????

Sorry, I didn't notice that you were confusing the client and the server.
The service object does not exist on the client. What's on the client (in
your case) is a proxy class generated from the WSDL file which .NET

produced

from the metadata on the server. .NET chose to create a proxy class with a
Header object called HeaderValue. That's not within your control.

So, don't worry about the name difference, as MyClass on the client and
MyClass on the server are two classes with almost no relationship between
them.

In other words, just use what works, HeaderValue, and don't expect the
client and server to be the same thing.

John

[John Saunders]

"Debasish Pramanik" <de***************@Assetlink.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

Hi John,

Thanks for the reply !!

I have seen some site whee they say it depend upon the namespace that you
can provide the attribute that controls the name. Do you have any idea
about
that.

No, sorry, I've never heard of anything like that. As far as I know, if you
use a Microsoft-generated proxy class, then you have to put up with
Microsoft-generated names.

John