- From: Christopher B Ferris <chrisfer@us.ibm.com>
- Date: Fri, 20 Jan 2006 19:27:32 -0500
- To: WS-Addressing <public-ws-addressing@w3.org>
- Message-ID: <OFBDD0B8F8.8775488C-ON852570FC.004764C7-852570FD.00028456@us.ibm.com>
<decloak> Mark writes: > The SOAP 1.2 Addressing 1.0 Feature changes the SOAP 1.1/HTTP binding > when "http://www.w3.org/@@@@/@@/addressing/anonymous" is not > specified for the response endpoint as described in 3.6.1 SOAP 1.1/HTTP. How does it *change* the SOAP/HTTP binding? In fact, I don't believe that it does change the binding in any way. All the SOAP11/HTTP binding says is how to stick a SOAP message into an HTTP request and HTTP response. It doesn't make any claims about I think that there is a misunderstanding about existance of a relationship between MEPs at different layers. In fact, I believe that there is none, nor should there be one. The fact that absent WS-A MAPs that a WSDL R/R MEP and the SOAP R/R MEP are seemingly the same is merely a coincidence. I also think that it was a mistake for the WS-I BP to impose some sort of artificial association between a WSDL oneway operation and a non-existant oneway SOAP MEP such that they disallowed a SOAP envelope in the HTTP response message. WS-RM has an important use case that requires exploiting the HTTP response message to send back a SequenceAcknowledgement. Just because the WSDL says that the operation is a oneway shouldn't preclude a SOAP envelope in the response with the SequenceAcknowledgement information. A WSDL oneway operation only means that the *application* is not expecting an application-level response in the form of a SOAP message. If the WS-I BP permits a fault to be transmitted/transferred back on the HTTP response, why not some other infrastructure-level signal such as an RM ack or a non-repudiation acknowledgement? </decloak> Cheers, Christopher Ferris STSM, Emerging e-business Industry Architecture email: chrisfer@us.ibm.com blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440 phone: +1 508 377 9295 public-ws-addressing-request@w3.org wrote on 01/19/2006 08:00:54 PM: > > i067 / i068 > > 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.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). > > 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>. 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 "http://www.w3.org/@@@@/@@/addressing/anonymous" is not > specified for the response endpoint as described in 3.6.1 SOAP 1.1/HTTP. > > > -- > Mark Nottingham http://www.mnot.net/ > >
Received on Saturday, 21 January 2006 00:27:47 UTC