This text file contains sample code fragments from:
Section 9.2 - Interface Definition
Chapter 9 - Fundamental WSDL 2.0: New Features and Design Options
Book - Web Service Contract Design & Versioning for SOA
Series - Prentice Hall Service-Oriented Computing Series from Thomas Erl
Site - www.soabooks.com


<interface name="..." extends="..." styleDefault="...">
  <fault name="..." element="..." />
  <operation name="..." pattern="..." style="..."
    wsdlx:safe="...">
      <input messageLabel="..." element="..." />
      <output messageLabel="..." element="..." />
      <infault ref="..." messageLabel="..." />
      <outfault ref="..." messageLabel="..." />
  </operation>
</interface>

Example 9.1 - The WSDL 2.0 interface construct with possible child elements.


<interface name="ifPurchaseOrderLog">
  <operation name="opLogOrder"
    pattern="http://www.w3.org/2006/01/wsdl/out-only">
    <output messageLabel="Out" element="po:orderLog"/>
  </operation>
</interface>

Example 9.2 - An interface construct with one operation element.


<interface name="ifPurchaseOrder" extends="tns:ifPurchaseOrderLog" >
  <operation name="opChangeOrder"
    pattern="http://www.w3.org/2006/01/wsdl/in-out">
    <input messageLabel="In" element="po:purchaseOrder "/>
    <output messageLabel="Out" element="po:acknowledgement"/>
  </operation>
  <operation name="opCancelOrder"
    pattern="http://www.w3.org/2006/01/wsdl/in-out">
    <input messageLabel="In" element="po:poNumber"/>
    <output messageLabel="Out" element="po:acknowledgement"/>
  </operation>
</interface>

Example 9.3 - An interface construct that inherits from another interface construct as per the extends attribute.


<interface name="ifPurchaseOrderLog"
  styleDefault="http://www.w3.org/ns/wsdl/style/iri">
  <operation name="opLogOrder"
    pattern="http://www.w3.org/2006/01/wsdl/out-only">
    <output messageLabel="Out" element="po:orderLog"/>
  </operation>
</interface>

Example 9.4 - The interface element's styleDefault attribute set to the IRI style.


<types>
  <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://actioncon.com/schema/po"
    targetNamespace="http://actioncon.com/schema/po"
    elementFormDefault="qualified">
    <xsd:element name="invalidOrder"
      type="invalidOrderType"/>
    <xsd:complexType name="invalidOrderType">
      <xsd:sequence>
        <xsd:element name="PODate" type="xsd:date"/>
        <xsd:element name="OrderID" type="xsd:string"/>
        <xsd:element name="Desc" type="xsd:string"/>
      </xsd:sequence>
    </xsd:complexType>
  </xsd:schema>
</types>

Example 9.5 - The types construct establishing the invalidOrderType XML Schema type.


<interface name="ifPurchaseOrder" extends="tns:ifPurchaseOrderLog" >
  <fault name="invalidOrderFault" element="po:invalidOrder"/>
  <operation name="opChangeOrder"
    pattern="http://www.w3.org/2006/01/wsdl/in-out">
    <input messageLabel="In" element="po:purchaseOrder "/>
    <output messageLabel="Out" element="po:acknowledgement"/>
    <outfault ref="tns:invalidOrderFault" messageLabel="Out/>
  </operation>
  <operation name="opCancelOrder"
    pattern="http://www.w3.org/2006/01/wsdl/in-out">
    <input messageLabel="In" element="po:poNumber"/>
    <output messageLabel="Out"
      element="po:acknowledgement"/>
    <outfault ref="tns:invalidOrderFault" messageLabel="Out/>
  </operation>
</interface>

Example 9.6 - The outfault elements within two operation constructs that reference the invalidOrderType type.


<binding name="bdPurchaseOrder-SOAP12HTTP"
  interface="tns:ifPurchaseOrder" >
  <fault ref="tns:invalidOrderFault" soap12:code="soap12:Sender"/>
  <operation ref="tns:opChangeOrder" .../>
  <operation ref="tns:opCancelOrder" .../>
</binding>

Example 9.7 - A fault element bound to the binding element that also contains two operation elements.


<soap:Envelope xmlns:soap=
  "http://www.w3.org/2003/05/soap-envelope"
  xmlns:po="http://actioncon.com/schema/po" ...>
  <soap:Body>
    <soap:Fault>
      <soap:Code>
        <soap:Value>soap:Sender</soap:Value>
      </soap:Code>
      <soap:Detail>
        <po:invalidOrder>
          <po:PODate>02-23-2008</po:PODate>
          <po:OrderID>1234</po:OrderID>
          <po:Desc>
            The required order party ID is missing.
          </po:Desc>
        </po:invalidOrder>
      </soap:Detail>
    </soap:Fault>
  </soap:Body>
</soap:Envelope>

Example 9.8 - A sample runtime SOAP fault message.


<operation name="opChangeOrder"
  pattern="http://www.w3.org/2006/01/wsdl/in-out">
  <input messageLabel="In" element="po:purchaseOrder "/>
  <output messageLabel="Out" element="po:acknowledgement"/>
</operation>

Example 9.9 - A WSDL 2.0 operation definition based on the In-Out MEP.