This text file contains sample code fragments from:
Chapter 15 - Legacy Encapsulation Patterns
Book - SOA Design Patterns
Series - Prentice Hall Service-Oriented Computing Series from Thomas Erl
Site - www.soabooks.com


<definitions ...>
  <types>
    <!-- type definition for the legacy header data -->
    <element name="securityheader">
      <complexType>
        <sequence>
          <element name="securetoken" type="xsd:string"/>
        </sequence>
      </complexType>
    </element>
    ...
  </types>
  ...
  <!-- message definition for the legacy header -->
  <message name="appealAssessmentHeaderData">
    <part name="header" element="securityheader"/>
    <!-- Other technical information can be included here -->
  </message>
  ...
  <!-- SOAP header declaration in the WSDL binding -->
  <binding name="AppealAssessmentBinding" type=
    "tns:AppealAssessmentService">
    <soap:binding style="document" transport=
      "http://schemas.xmlsoap.org/soap/http"/>
    <operation name="appealAssessment">
      <soap:operation soapAction=""/>
      <input>
        <soap:body message=
          "tns:appealAssessmentInputMessage" use="literal"/>
        <soap:header message="appealAssessmentHeaderData"
          part="header" use="literal"/>
      </input>
      <output>
        <soap:body message=
          "appealAssessmentOutputMessage" use="literal"/>
      </output>
    </operation>
  </binding>
  ...
</definitions>

Example 15.4 - These code fragments show how legacy details can be isolated inside SOAP headers. Note the SOAP header is considered implicit because it is not referred to in the portType construct.