Re: Action item for issue i021

Hugo,

AIUI, Paco gave SOAP binding as an example while proposing a solution 
that is applicable to non-soap bindings also.
Doesn't the soap-module approach for WSDL 2.0 you suggest make that soap 
binding specific?

Prasad

Hugo Haas wrote:

>* Francisco Curbera <curbera@us.ibm.com> [2005-03-28 14:43-0500]
>[..]
>  
>
>>The approach is as follows: introduce a marker to be used in both WSDL
>>    
>>
>1.1
>  
>
>>and WSDL 2.0 bindings to indicate the fact that a service uses and
>>    
>>
>requires
>  
>
>>clients to use WSA message information headers in every service
>>    
>>
>invocation.
>  
>
>>I think it is generally accepted that this indication belongs in the
>>    
>>
>WSDL
>  
>
>>binding, since one could possibly want to deploy the same interface
>>    
>>
>with
>  
>
>>different protocols bindings in some of which WSA usage may not be
>>    
>>
>common,
>  
>
>>including pre-WSA "legacy" SOAP bindings.
>>    
>>
>
>Such a marker is only necessary for WSDL 1.1. Now that we have defined
>modules for our SOAP Bindings, we can use WSDL 2.0's wsoap:module
>declaration as follows:
>
>[..]
>  
>
>>WSDL 2.0 example:
>>
>><binding name="reservationSOAPBinding"
>>          interface="tns:reservationInterface"
>>          type="http://www.w3.org/2004/08/wsdl/soap12"
>>
>>    
>>
>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
>  
>
>>    <wsaw:UsingAddressing wsdl:required="true"/>
>>    <operation ref="tns:opCheckAvailability"
>>
>>    
>>
>wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
>  
>
>>    <fault ref="tns:invalidDataFault"  wsoap:code="soap:Sender"/>
>>
>></binding>
>>    
>>
>
><binding name="reservationSOAPBinding"
>          interface="tns:reservationInterface"
>          type="http://www.w3.org/2004/08/wsdl/soap12"
>          wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
>
>    <wsoap:module uri="http://www.w3.org/2005/03/addressing/module"
>wsdl:required="true"/>
>
>    <operation ref="tns:opCheckAvailability"
>       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
>
>    <fault ref="tns:invalidDataFault"  wsoap:code="soap:Sender"/>
>
></binding>
>
>Regards,
>
>Hugo
>
>  
>