W3C home > Mailing lists > Public > www-ws-desc@w3.org > March 2003

Re: SOAP Response pattern and our MEPs

From: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>
Date: Mon, 24 Mar 2003 09:52:07 +0100
Message-ID: <3E7EC737.6050807@crf.canon.fr>
To: Jacek Kopecky <jacek@systinet.com>
CC: WS-Description WG <www-ws-desc@w3.org>

Yes of course, the mapping goes from WSDL to SOAP! :-)

Jean-Jacques.

Jacek Kopecky wrote:
> Of course, yes. 8-)
> 
> But the mapping goes the other way - one doesn't map SOAP MEPs onto WSDL
> MEPs; instead WSDL MEPs used by WSDL operations are mapped to SOAP MEPs.
> So yes, I also have in mind to allow WSDL request/response operations to
> use SOAP Request/response MEP.
> 
> Best regards,
> 
>                    Jacek Kopecky
> 
>                    Senior Architect, Systinet Corporation
>                    http://www.systinet.com/
> 
> 
> 
> 
> 
> On Fri, 2003-03-21 at 15:47, Jean-Jacques Moreau wrote:
> 
>>Sounds good. I suspect you also have in mind to map the SOAP 
>>Request-Response MEP to the WSDL request-response pattern?
>>
>>Jean-Jacques.
>>
>>Jacek Kopecky wrote:
>>
>>>Hi all,
>>>
>>>I'm trying here to start fulfilling my action item on relating the SOAP
>>>Response MEP with WSDL MEPs (I think this is what the MEP work has
>>>transformed my action item into.)
>>>
>>>"The SOAP Response MEP defines a pattern for the exchange of a non-SOAP
>>>message acting as a request followed by a SOAP message acting as a
>>>response. In the absence of failure in the underlying protocol, this MEP
>>>consists of exactly two messages, only one of which is a SOAP message." 
>>>[http://www.w3.org/TR/soap12-part2/#soapresmep]
>>>
>>>So at the first look, this MEP can be used by operations following the
>>>WSDL Request/Response (I think we agreed to add that MEP) pattern.
>>>
>>>Let's now look at the primary intended usage of this SOAP MEP - it's an
>>>HTTP GET request with a response containing a SOAP Envelope. From this
>>>point of view, there is only the target URI and the request message as
>>>such is empty. Therefore, in the cases where there are no parameters
>>>marshaled in the URI, the SOAP Response MEP could also be used by
>>>operations following the output-only WSDL MEP.
>>>
>>>I suggest that our SOAP binding support mapping request/response
>>>operations onto the SOAP Response MEP (probably using some way of
>>>marshaling the request message into the request URI for HTTP GET -
>>>I think the URI replacement algorithm should fit here); and I also
>>>suggest that our SOAP binding support mapping output-only operations
>>>onto the SOAP Response MEP, thus enriching the current capabilities of
>>>our SOAP binding. 8-)
>>>
>>>Best regards,
>>>
>>>                   Jacek Kopecky
>>>
>>>                   Senior Architect, Systinet Corporation
>>>                   http://www.systinet.com/
>>>
>>>
>>>
>>>
>>>
> 
> 
Received on Monday, 24 March 2003 03:52:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:23 GMT