-
Payload Construction. When formulating
the SOAP envelope to be transmitted the contents of the
payload (i.e., the contents of the soap:Body element information item
of the SOAP envelope) MUST be what is defined by the
corresponding Message Reference component. This is subject
to optimization by a feature that is in use which may affect
serialization, such as MTOM [MTOM]. The
following default binding rules MUST be adhered to:
-
If the value of the
[{message content model}] property of
the Message Reference component is #any then
the payload MAY be any one XML element.
-
If the value is #none then the
payload MUST be empty.
-
If the value is #element then the
payload will be the element information item identified by the
[{element}] property of the Message
Reference component.
-
If the Message Reference component is declared
using a non-XML type system (as considered in the Types
section of [WSDL-PART1]) then additional
binding rules MUST be defined to indicate how to map those
components into the SOAP envelope.
NOTE:
This SOAP binding only allows one single element in
SOAP body.
-
SOAPAction. If a value for the {soap
action} property of a Binding Operation component has NOT
been specified then the SOAP Action Feature (see [SOAP12-PART2]) has NO value assigned by the Binding
component.
-
SOAP MEP Selection. If the Interface
Operation component's
[{message exchange pattern}] property
has the value http://www.w3.org/2004/08/wsdl/in-out then the
default value of the {soap mep} property for the
corresponding Binding Operation component is
http://www.w3.org/2003/05/soap/mep/request-response/
identifying the SOAP Request-Response Message Exchange
Pattern as defined in [SOAP12-PART2]. If the
Inteface Operation component has any other value for the
[{message exchange pattern}] property,
then no default value is defined for the {soap mep} property
of the corresponding Binding Operation component.
-
HTTP Method Selection. This default
binding rule is applicable when the value of the {soap
underlying protocol} property of the Binding component is
http://www.w3.org/2003/05/soap/bindings/HTTP/. If
the {soap mep} property of the Binding Operation component
has the value
http://www.w3.org/2003/05/soap/mep/request-response/
then the default value of the {http method} property is
POST. If the {soap mep} property of the Binding
Operation component has the value
http://www.w3.org/2003/05/soap/mep/soap-response/
then the default value of the {http method} property is
GET.
-
HTTP URI Generation. This default
binding rule is applicable when the value of the {soap
underlying protocol} property of the Binding component is
http://www.w3.org/2003/05/soap/bindings/HTTP/. If
the {soap mep} property of the Binding Operation component
has the value
http://www.w3.org/2003/05/soap/mep/soap-response/
then the URI to execute the HTTP GET against MUST be
generated using the HTTP binding's rules for generating a
URI for HTTP GET (see [WSDL HTTP Binding]). The
input serialization format of
x-www-form-urlencoded is the only supported
serialization format for HTTP GET in the SOAP Response
Message Exchange Pattern.
Ed. Note:
Input serialization for HTTP GET in SOAP HTTP binding
Use of a different input serialization format
requires introduction of either a new MEP or a new
binding. The Working Group considered the limitations of
the x-www-form-urlencoded serialization
format (see points
#2 and #3 of Binding message content to URI
analysis). It decided that the limitations of the
serialization format, which could potentially be solved
by a serialization format extension, were not
sufficiently broad enough to warrant allowing
extensibility in input serialization for the
soap-response MEP. The Working Group solicits the
public's feedback on this decision.
