SOAP headers offer a method for passing data to and from an XML Web service method if the data is not directly related to the XML Web service method's primary functionality. For instance, an XML Web service might contain several XML Web service methods that each require a custom authentication scheme. Instead of adding parameters to each XML Web service method for the custom authentication scheme, aSoapHeaderAttribute, referring to a class deriving from , can be applied to each XML Web service method. The implementation for the class deriving from handles the custom authentication scheme. In this manner, the XML Web service method implements only the functionality specific to it and adds additional functionality using a SOAP header.
The following list outlines the basic steps to receiving and processing a SOAP header:
Create a class that derives from representing the data passed into the SOAP header.
Add a member to the class implementing an XML Web service or an XML Web service client proxy class, of the type created in the first step.
Within the XML Web service method or XML Web service client code, access the MemberName property to process the data sent in the SOAP header.