Re: Mapping WSDL MEPs to SOAP MEPs

The latest SOAP/HTTP binding proposed edited rec 
(http://www.w3.org/TR/2006/PER-soap12-part2-20061219/)
includes the support of an optional response (with a 202 response code 
and so on).
I hope that the document state (proposed edited rec) is sufficient for 
us to use it in the WSDL2.0 specification.
    Youenn


Sanjiva Weerawarana wrote:
>
> youenn fablet wrote:
>>
>> Reviewing the soap binding, I have the following comments.
>>
>> As of today, the SOAP binding defines how to map the inout mep to the 
>> request-response and soap-response meps.
>> The mapping from in-only and robust in-only meps to SOAP meps are not 
>> defined, which makes difficult or at least not very interoperable the 
>> use of these two WSDL meps with the SOAP binding.
>
> The problem is the SOAP spec doesn't support them.
>
>> It seems that the newest version of the SOAP1.2 specification 
>> (http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html) will 
>> provide the SOAP/HTTP binding with the support of the 
>> request-optional response mep. This mep fits well with the 
>> robust-in-only mep at least.
>> It may therefore be interesting to add in the WSDL SOAP binding 
>> section a robust-inonly mep to soap mep mapping description.
>
> Is this a released version of the SOAP spec? We can't possibly depend 
> on a non-REC version.
>
>> Concerning the in-only mep, the situation seems less clear. Of course 
>> we could also bind the in-only mep to the request-optional response 
>> mep. On the other hand, a SOAP1.2 one way mep is under way but has no 
>> support in the SOAP1.2/HTTP binding.
>
> That's really stupid that XMLP let it happen like that but I'm unclear 
> what we can do now.
>
> Sanjiva.