3.1 UsingAddressing Extension Element

WS-Addressing defines an empty global element, wsaw:UsingAddressing, that may be used to indicate that an endpoint conforms to the WS-Addressing specification. The wsdl:required attribute MAY be used to indicate whether WS-Addressing Message Addressing Properties are required in messages received from service requesters.

A wsaw:UsingAddressing element with a wsdl:required attribute whose value is "true" indicates that messages exchanged with the endpoint MUST contain WS-Addressing Message Addressing Properties. A wsaw:UsingAddressing element with a wsdl:required attribute whose value is "false" indicates that the endpoint will accept input messages with or without WS-Addressing header blocks, and MAY generate output messages containing WS-Addressing headers. If a SOAP binding is used and WS-Addressing header blocks are not present in an input message then WS-Addressing header blocks encoded in the corresponding output message MUST NOT be required to be understood using the SOAP mustUnderstand mechanism.

The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding element. Alternatively, the wsaw:UsingAddressing element MAY instead be included as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to indicate compliance with WS-Addressing for a specific endpoint only.

The inclusion of the wsaw:UsingAddressing element indicates that the applicable WS-Addressing specifications are supported may change the constraints of the WSDL binding being used.   Specifically, when included in a SOAP binding, the wsaw:UsingAddressing marker identifies the use of Web Services Addressing 1.0 bound to SOAP as defined by Web Services Addressing 1.0 - SOAP Binding[WS-Addressing-SOAP]  with the following extension to SOAP xx/HTTP:

T   The extension allows a SOAP1.x/HTTP binding to use a separate connection for sending response messages, instead of using the same HTTP connection. This extension allows SOAP 1.x/HTTP to be used asynchronously as follows.

The response message MAY be sent over the same HTTP channel over which the request was received or by opening a separate connection. When the value of the [reply endpoint] in the request message contains the anonymous URI as the address, the response MUST be sent over the same HTTP channel.  However, when the value of [reply endpoint] contains an address that is different than the anonymous URI, this extension for the SOAP/HTTP binding requires the following

• ·The receipt of the request message MUST be acknowledged with a status message (202) by the receiver using the HTTP connection that generated the request. The receipt message MUST contain an empty SOAP body. 

• ·The actual response MUST be sent using a separate connection using the address value of the response message specified by [reply endpoint].