This text file contains sample code fragments from:
Section 14.1 - Modularization Mechanisms
Chapter 14 - Advanced WSDL Part I: Modularization, Extensibility, MEPs, and Asynchrony
Book - Web Service Contract Design & Versioning for SOA
Series - The Prentice Hall Service Technology Series from Thomas Erl
Site - www.servicetechbooks.com


<definitions targetNamespace=
  "http://actioncon.com/contract/POSoap11"
  xmlns:tns="http://actioncon.com/contract/POSoap11"
  xmlns:abs="http://actioncon.com/contract/po"
  xmlns="http://schemas.xmlsoap.org/wsdl/"
  xmlns:po="http://actioncon.com/schema/purchasing"
  xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/">
  <import
    namespace="http://actioncon.com/contract/po"
    location="http://actioncon.com/contract/po"/>
  <binding name="bdPO-SOAP11HTTP" type="abs:ptPurchaseOrder">
    <soap11:binding style="document"
      transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="opSubmitOrder">
      <input><soap11:body use="literal"/></input>
      <output><soap11:body use="literal"/></output>
    </operation>
    <operation name="opCheckOrderStatus">
      <input><soap11:body use="literal"/></input>
      <output><soap11:body use="literal"/></output>
    </operation>
    <operation name="opChangeOrder">
      <input><soap11:body use="literal"/></input>
      <output><soap11:body use="literal"/></output>
    </operation>
    <operation name="opCancelOrder">
      <input><soap11:body use="literal"/></input>
      <output><soap11:body use="literal"/></output>
    </operation>
  </binding>
  <service name="svPurchaseOrder">
    <port name="purchaseOrder-soap11http"
      binding="tns:bdPO-SOAP11HTTP">
      <soap11:address location=
        "http://actioncon.com/services/soap11/po"/>
      </port>
    </service>
</definitions>

Example 14.1 - A WSDL definition containing a concrete description bound to SOAP 1.1 and importing an abstract description.


<definitions targetNamespace=
  "http://actioncon.com/contract/POSoap12"
  xmlns:tns="http://actioncon.com/contract/POSoap12"
  xmlns:abs="http://actioncon.com/contract/po"
  xmlns="http://schemas.xmlsoap.org/wsdl/"
  xmlns:po="http://actioncon.com/schema/purchasing"
  xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
  xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">
  <import
    namespace="http://actioncon.com/contract/po"
    location="http://actioncon.com/contract/po"/>
  <binding name="bdPO-SOAP12HTTP" type="abs:ptPurchaseOrder">
  <soap12:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="opSubmitOrder">
    <soap12:operation soapAction=
      "http://actioncon.com/submitOrder/request"
        soapActionRequired="true" required="true"/>
      <input><soap12:body use="literal"/></input>
      <output><soap12:body use="literal"/></output>
    </operation>
    <operation name="opCheckOrderStatus">
    <soap12:operation soapAction=
      "http://actioncon.com/submitOrder/request"
        soapActionRequired="true" required="true"/>
      <input><soap12:body use="literal"/></input>
      <output><soap12:body use="literal"/></output>
    </operation>
    <operation name="opChangeOrder">
    <soap12:operation soapAction=
      "http://actioncon.com/submitOrder/request"
        soapActionRequired="true" required="true"/>
      <input><soap12:body use="literal"/></input>
      <output><soap12:body use="literal"/></output>
    </operation>
    <operation name="opCancelOrder">
    <soap12:operation soapAction=
      "http://actioncon.com/submitOrder/request"
        soapActionRequired="true" required="true"/>
        <input><soap12:body use="literal"/></input>
        <output><soap12:body use="literal"/></output>
    </operation>
  </binding>
  <service name="svPurchaseOrder">
    <port name="purchaseOrder-http-soap12"
      binding="tns:bdPO-SOAP12HTTP">
      <soap12:address location=
        "http://actioncon.com/services/soap12/po"/>
    </port>
  </service>
</definitions>

Example 14.2 - A WSDL definition containing a concrete description bound to SOAP 1.2 and importing the same abstract description as the previous definition.


<include location=
  "http://actioncon.com/contract/PO-abstract.wsdl20"/>

Example 14.3 - The WSDL 2.0 include element.


<definitions ...>
  <types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:import namespace=
        "http://actioncon.com/schema/purchasing"
        schemaLocation=
        "http://actioncon.com/schema/purchaseOrder.xsd"/>
        <!-- imported types can be used here... -->
    </xsd:schema>
  </types>
  <!-- ...and here -->
</definitions>

Example 14.4 - A WSDL 1.1 types definition with an xsd:import element wrapped in an xsd:schema construct.


<description ...>
  <types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:import namespace=
        "http://actioncon.com/schema/purchasing"
        schemaLocation=
        "http://actioncon.com/schema/purchaseOrder.xsd"/>
      <!-- imported types can be used here... -->
    </xsd:schema>
  </types>
  <!-- ...but not here -->
</description>

Example 14.5 - A WSDL 2.0 types definition with an xsd:import element wrapped in an xsd:schema construct.


<description ...>
  <types>
    <xsd:import namespace=
      "http://actioncon.com/schema/purchasing"
      schemaLocation=
      "http://actioncon.com/schema/purchaseOrder.xsd"/>
  </types>
  <!-- imported types can be used here -->
</description>

Example 14.6 - A WSDL 2.0 types definition with a child xsd:import element.


<description ...>
  <types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      targetNamespace=
        "http://actioncon.com/schema/purchasing">
      <xsd:include schemaLocation=
        "http://actioncon.com/schema/purchaseOrderDetail.xsd"/>
    <!-- imported types can be used here... -->
    </xsd:schema>
  </types>
  <!-- ...and here -->
</description>

Example 14.7 - A WSDL 2.0 types definition with an xsd:include element wrapped in an xsd:schema construct.


<types>
  <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:import namespace=
      "http://actioncon.com/schema/purchasing"
      schemaLocation=
      "http://actioncon.com/schema/purchaseOrder.xsd"/>
    <xsd:import namespace=
      "http://actioncon.com/schema/common"
      schemaLocation=
      "http://actioncon.com/schema/common.xsd"/>
  </xsd:schema>
</types>

Example 14.8 - A types construct importing two XML Schema definitions. Types from both XML Schema documents will become available to the rest of the WSDL document.


<definitions targetNamespace=
  "http://actioncon.com/contract/po"
  xmlns:tns=" http://actioncon.com/contract/po"
  xmlns="http://schemas.xmlsoap.org/wsdl/"
  xmlns:po="http://actioncon.com/schema/purchasing"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <types>
    <xsd:schema targetNamespace=
      "http://actioncon.com/schema/common"
      xmlns="http://actioncon.com/schema/common"
      elementFormDefault="qualified">
      <xsd:simpleType name="ProductIDType">
        <xsd:restriction base="xsd:string">
          <xsd:pattern value="[A-Z]{2}[0-9]{4}"/>
        </xsd:restriction>
      </xsd:simpleType>
      <xsd:simpleType name="PriceType">
        <xsd:restriction base="xsd:decimal">
          <xsd:totalDigits value="8"/>
          <xsd:fractionDigits value="2"/>
        </xsd:restriction>
      </xsd:simpleType>
      <xsd:complexType name="AddressType">
        <xsd:sequence>
          <xsd:element name="line1" type="xsd:string"/>
          <xsd:element name="line2" type="xsd:string"
            minOccurs="0"/>
          <xsd:element name="city" type="xsd:string"/>
          <xsd:element name="state" type="xsd:string"/>
          <xsd:element name="postalCode" type="xsd:string"/>
          <xsd:element name="country" type="xsd:string"/>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:schema>
    <xsd:schema targetNamespace=
      "http://actioncon.com/schema/purchasing"
      xmlns="http://actioncon.com/schema/purchasing"
      xmlns:common="http://actioncon.com/schema/common"
      elementFormDefault="qualified">
      <!-- This import statement is required. -->
      <xsd:import namespace=
        "http://actioncon.com/schema/common"/>
      <xsd:element name="purchaseOrder" type=
        "PurchaseOrderType"/>
      <xsd:complexType name="PurchaseOrderType">
        <xsd:sequence>
          <xsd:element name="poNumber" type="xsd:int"/>
          <xsd:element name="poDate" type="xsd:date"/>
          <xsd:element name="billToParty" type="PartyType"/>
          <xsd:element name="shipToParty" type="PartyType"/>
          <xsd:element name="lineItems"
            type="LineItemsType"/>
        </xsd:sequence>
        <xsd:attribute name="version" type="xsd:decimal"/>
      </xsd:complexType>
      <xsd:complexType name="PartyType">
        <xsd:sequence>
          <xsd:element name="id" type="xsd:int"/>
          <xsd:element name="partyName" type="xsd:string"/>
          <xsd:element name="contactName"
            type="xsd:string"/>
          <xsd:element name="phone" type="xsd:string"/>
          <xsd:element name="address"
            type="common:AddressType"/>
        </xsd:sequence>
      </xsd:complexType>
      <xsd:complexType name="LineItemsType">
        <xsd:sequence>
          <xsd:element name="lineItem" type="LineItemType"
            maxOccurs="unbounded"/>
        </xsd:sequence>
      </xsd:complexType>
      <xsd:complexType name="LineItemType">
        <xsd:sequence>
          <xsd:element name="productID" type=
            "common:ProductIDType"/>
          <xsd:element name="productName"
            type="xsd:string"/>
          <xsd:element name="quantity" type="xsd:int"/>
          <xsd:element name="price"
            type="common:PriceType"/>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:schema>
  </types>
</definitions>

Example 14.9 - Multiple schema definitions embedded in a WSDL types element. The highlighted xsd:import statement allows one schema to reference types that reside in the other. Note that the xsd:import element does not have a schemaLocation attribute because the WSDL processor automatically knows where to find the definitions for types in this namespace (they are embedded in the same WSDL document).


<interface name="ifPurchaseOrderAdmin"
  extends="tns:ifPurchaseOrder">
  <operation name="opListOrders"
    pattern="http://www.w3.org/ns/wsdl/in-out">
    <input element="po:poListRequest"/>
    <output element="po:poListResponse"/>
  </operation>
</interface>

Example 14.10 - The ifPurchaseOrderAdmin interface element with an extends attribute pointing to the tns:ifPurchaseOrder interface element.