Table of contents

Appendices

2 WSDL SOAP Binding

The SOAP binding described in this section is an extension for [WSDL-PART1] to enable Web Services applications to use SOAP 1.2 [SOAP12-PART1]. This binding extends WSDL 2.0 by adding properties to the [Binding component] as defined in [WSDL-PART1]. In addition, an XML Infoset representation for these additional properties is provided, along with a mapping from that representation to the various component properties.

As allowed in [WSDL-PART1], a Binding component MAY exist without indicating a specific [Interface component] that it applies to. In this case there MUST NOT be any [Binding Operation] or [Binding Fault] components present in the Binding component.

The SOAP binding is designed with the objective of minimizing what needs to be explicitly declared for common cases. This is achieved by defining a set of default rules which apply for all Interface Operation components of an Interface component, unless specifically overidden on a per Interface Operation basis. Thus, if a given Interface Operation component is not referred to specifically, then all the default rules apply for that component. That is, per the requirements of [WSDL-PART1] all operations of an Interface component are bound by this binding.

Notice that there are no default binding rules defined for [Interface Fault components] by this binding. Thus, if a given Interface component has any Fault components, then such Interface components MUST be bound via Binding components which indicate a specific interface and contain as many Binding Fault components as there are Fault components in the Interface Fault component.

A subset of the HTTP properties specified in the HTTP binding defined in section [WSDL HTTP Binding] may be expressed in a SOAP binding when the SOAP binding uses HTTP as the underlying protocol, i.e. when the value of the {soap underlying protocol} property of the Binding component is http://www.w3.org/2003/05/soap/bindings/HTTP/. The properties that are allowed are the ones that describe the underlying protocol.

• {http version} as defined in [Specifying the HTTP Version]

• {http transfer coding} as defined in [Specifying the transfer coding]

• {http cookies} as defined in [Specifying the Use of HTTP Cookies]

• {http authentication scheme} and {http authentication realm} as defined in [Specifying HTTP Access Authentication]

When the SOAP Message Exchange Pattern is the SOAP Response MEP, the Binding Operation may use the {http location} property defined in [Binding Operations]. When such a location is specified, the Endpoint component also follows the rules for constructing the address from the [{address}] property and the {http location} property values.