W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2006

i067 / i068 / cr15 resolution

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Tue, 24 Jan 2006 14:42:48 -0800
Message-Id: <2D0331A0-7F39-4D98-9C41-12A8AFF6E843@bea.com>
To: WS-Addressing <public-ws-addressing@w3.org>

... as accepted by the group:

i067 / i068  --> CR15

3.5 Use of Anonymous Address in SOAP

3.5.1 SOAP 1.1/HTTP

When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified  
for the response endpoint then there is no change to the SOAP 1.1/ 
HTTP binding.

3.5.2 SOAP 1.2

When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified  
for the response endpoint and the request is the request part of a  
SOAP request-response MEP [soap 1.2 adjuncts ref], then any response  
MUST be the response part of the same SOAP request-response MEP [soap  
1.2
adjuncts ref].

3.6 Use of Non-Anonymous Address in SOAP

3.6.1 SOAP 1.1/HTTP

When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not  
specified for the response endpoint, then the request SHOULD be part  
of a binding that supports not returning a SOAP envelope in the HTTP  
response, such as [URI for binding doc].  Any response message SHOULD  
be sent using a separate connection and using the address value  
specified by response endpoint. Note that other specifications MAY  
define special URIs that have other behaviours (similar to the  
anonymous URI).

3.6.2 SOAP 1.2

When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not  
specified for the response endpoint, then any response SHOULD not be  
the response part of the same SOAP request-response MEP [soap 1.2  
adjuncts ref].  For instance, a SOAP 1.2 HTTP binding that supports a  
one-way MEP could put the reply message in a separate one-way MEP and  
a separate HTTP request. As in SOAP 1.1/HTTP, note that other  
specifications MAY define special URIs that have other behaviours  
(similar to the anonymous URI).


--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Tuesday, 24 January 2006 22:43:04 GMT

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