This text file contains sample code fragments from:
Section 15.2 - Message Dispatch Challenges
Chapter 15 - Advanced WSDL Part II: Message Dispatch, Service Instance Identification, and Non-SOAP HTTP Binding
Book - Web Service Contract Design & Versioning for SOA
Series - The Prentice Hall Service Technology Series from Thomas Erl
Site - www.servicetechbooks.com
123456
Example 15.8 - An incoming SOAP message that is suitable for both the opCheckOrderStatus and opCancelOrder operations.
Example 15.9 - Two different global elements reusing the same underlying complex type.
Example 15.10 - The global element declarations from Example 15.9 assigned to part elements for two different messages.
123456
Example 15.11 - An instance of the input SOAP message from Example 15.9.
Example 15.12 - The soapAction attribute of the soap11:operation extensibility element assigned a SOAP action value.
Example 15.13 - The soapAction attribute of the soap12:operation extensibility element assigned a SOAP action value and the soapActionRequired attribute set to "true."
...
Example 15.14 - The soapbind:action extensibility attribute set to a SOAP Action value.
Example 15.15 - Updated SOAP 1.1 binding elements with populated soapAction attributes.
...
Example 15.16 - The wsam:Addressing policy assertion associated with a portType element.
...
Example 15.17 - The wsaw:Action attribute added to the abstract input message definition.
...
...
Example 15.18 - The populated wsaw:Action attribute as part of an input element.
http://actioncon.com/services/soap12/purchaseOrder
http://actioncon.com/action/opSubmitOrder
...
Example 15.19 - The resulting SOAP message with the corresponding wsa:Action header block containing the same value of the wsaw:Action attribute.