SOAP Header name vs type

[EJSawyer]

In the process of building a SOAP client for a third-party service, I have
created a "dummy" service running on my local machine to debug against. I
have the dummy service working pretty well, but I've discovered that the WSDL
for my service has a subtle difference from the third-party service's WSDL
(which is also ASP.Net).

Specifically, the service requires a SOAP header, and in the WSDL, the
header is declared with the name= and type= as *different* from each other.
In my code, both of these values are derived from the class name of my
SOAPHeader-derived type.

Is there any way to override the name and/or type in my code?

Thanks,
Erik J Sawyer

 

[EJSawyer]

I kept poking around and found it: the TypeName parameter to the
XmlTypeAttribute applied to the class.