"soap12:body" - Binding for SOAP Body

WSDL Tutorials - Herong's Tutorial Examples

∟WSDL 1.1 Binding Extension for SOAP 1.2

∟"soap12:body" - Binding for SOAP Body

This section describes 'soap12:body', a SOAP extension element that specifies how the SOAP Body should be constructed in the SOAP message for an operation input and output. 'literal' means no encoding.

"soap12:body" is a SOAP extension element used as a sub element of the "wsdl:input" or "wsdl:output" element inside the "wsdl:binding" and "wsdl:operation" element structure. "soap12:body" is used to provide information on how the content of the SOAP Body element is constructed. The syntax of "soap12:body" looks like this:

<wsdl:definitions ...>
  <wsdl:binding ...>
    <wsdl:operation ...>
      <wsdl:input>
        <soap12:body parts="nmtokens" use="literal|encoded"
          encodingStyle="list" namespace="uri"/>
      </wsdl:input>
      <wsdl:output>
        <soap12:body parts="nmtokens" use="literal|encoded"
          encodingStyle="list" namespace="uri"/>
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
</wsdl:definitions>

Notes on the "soap12:body" element:

parts="nmtokens" - Indicates with part or parts defined in the input or output message (specified through the "wsdl:portType" element) are used to construct this SOAP Body. If not provided, all parts are used.
use="literal|encoded" - Indicates whether the message part(s) should be used as is (literal) or encoded. This is a required attribute. If use="literal", the message part(s) are referring to concrete schema definition(s) and no encoding is needed. If use="encoded", the message part(s) are referring to abstract schema definition(s) and concrete message can be produced by applying the specified encoding style.
encodingStyle="list" - Indicates encoding style(s) to be used in case of use="encoded".
namespace="uri" - Indicates the namespace to be used for SOAP Body sub elements.

If style="rpc" is specified for this operation, each message part is a parameter for the operation and appears inside a wrapper element within the SOAP Body. The wrapper element is assigned a local name of the operation name and a namespace name of the value of the namespace attribute of the soap12:body element. Each message part is carried as a child element of the wrapper element. Each parameter element is assigned a local name of the value of the name attribute of the corresponding wsdl:part element and a namespace name with no value.

If style="document" is specified for this operation, Child elements of the soap:Body must be elements as defined by the global element declarations identified by the respective QName values of the element attributes of the wsdl:part element children of the corresponding wsdl:message element. The message parts appear as child elements of the soap:Body element and there are no additional wrappers.

Here is an example of "soap12:operation" element:

  <wsdl:binding name="helloBinding" type="hy:helloPortType">
    <soap12:binding style="document"
      transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="Hello">
      <soap12:operation
        soapAction="https://www.herongyang.com/Service/Hello"/>
      <wsdl:input name="helloInput">
        <soap12:body use="literal"/>
      </wsdl:input>
      <wsdl:output name="helloOutput">
        <soap12:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>

In this example,

use="literal" indicates that no encoding is needed. My message parts for "helloInput" and "helloOutput" have concrete schema definitions.
parts="nmtokens" is not specified. So all message parts defined for "helloInput" should be used to construct the SOAP Body for the SOAP request. Add all message parts defined for "helloOutput" should be used to construct the SOAP Body for the SOAP response.