W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2005

i059: WS-Addressing SOAP Binding proposal

From: David Orchard <dorchard@bea.com>
Date: Fri, 16 Dec 2005 16:34:03 -0800
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9C06B8A9@repbex01.amer.bea.com>
To: <public-ws-addressing@w3.org>
Here's a quick first cut proposal at what the WS-A SOAP binding doc
updates would be to support one-way meps and async.

 


3.5 Use of Anonymous Address in SOAP


When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for
the response endpoint, the underlying SOAP protocol binding provides a
channel to the specified endpoint. Any underlying protocol binding
supporting a request-response message exchange pattern provides such a
channel for response messages. For instance, the SOAP 1.2 HTTP
binding[SOAP 1.2 Part 2: Adjuncts
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2004/ws/addressing/ws-addr-soap
.html#SOAP12-PART2#SOAP12-PART2> ] puts the reply message from the SOAP
request-response MEP in the HTTP response.

 


3.6 Anonymous Address not used in SOAP


When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified
for the response endpoint, the underlying SOAP protocol binding is not
used as a channel to the specified endpoint.  An additional underlying
protocol binding provides a channel for response messages.  For
instance, a SOAP 1.2 HTTP binding that supports a one-way MEP would put
the reply message in an HTTP request.

 


4. SOAP 1.1 Addressing 1.0 Extension


The SOAP 1.1 Addressing 1.0 Extension defines a set of SOAP header
blocks and SOAP 1.1 HTTP Binding modification to support the SOAP 1.2
Addressing 1.0 Feature described in 2. SOAP 1.2 Addressing 1.0 Feature
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2004/ws/addressing/ws-addr-soap
.html#s12feature#s12feature> .  This SOAP 1.1 extension is provided for
backwards compatibility only.

 


Addition to 4.2 Description


The SOAP 1.2 Addressing 1.0 Feature changes the SOAP 1.1/HTTP binding
when the anonymous address is not used.  In this case, the receiver of a
message MUST respond with a 202 status code and an empty HTTP body, aka
no SOAP envelope.  If a non-anonymous address is used, the outbound
message MUST be sent using a separate connection using the address value
of the specified by appropriate response endpoint 

 

Cheers,

Dave

 
Received on Saturday, 17 December 2005 00:34:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:10 GMT