W3C home > Mailing lists > Public > public-ws-addressing@w3.org > April 2005

Re: NEW ISSUE: How to determine the value of the [destination] property from WSDL? [i056]

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Wed, 13 Apr 2005 15:15:49 -0700
Message-Id: <e1391eaae89f798584c44749882ff702@bea.com>
Cc: public-ws-addressing@w3.org
To: Anish Karmarkar <Anish.Karmarkar@oracle.com>

This is now issue 056;
   http://www.w3.org/2002/ws/addr/wd-issues/#i056


On Apr 10, 2005, at 11:54 PM, Anish Karmarkar wrote:

>
> During last week's concall I took an action to raise an issue regd the  
> determination of the value of the [destination] property by looking at  
> the WSDL description. Here it is:
>
> * Title - How to determine the value of the [destination] property  
> from WSDL?
>
> * Description -
> The WSDL binding spec does not define how to determine the value of  
> the [destination] property when sending messages to a Web service  
> described in WSDL (and when WS-Addressing is also being used for that  
> Web service).
>
> * Justification -
> The WSDL binding spec [1] says: "Web Services Addressing 1.0 - WSDL  
> Binding (this document) defines how the abstract properties defined in  
> Web Services Addressing 1.0 - Core are described using WSDL."
> The [destination] property is required when using WS-Addressing [2],  
> but the WSDL binding spec does not define how this abstract property  
> is described using WSDL.
>
> * Target -
> WSDL Binding
>
> * Proposals -
>
> Here are five proposals to resolve this issue:
>
> 1) In the absence of additional information, the value of the  
> destination property is the same as the value of the  
> wsdl20:endpoint/@address attribute in case of WSDL 2.0 or the value of  
> {http:address|soapbind:address}/@location attribute in case of WSDL  
> 1.1.
>
> 2) Modify the proposal at [3] (for issue i021) as follows:
> i) allow the element wsaw:UsingAddressing to be a child element of  
> wsdl20:endpoint/wsdl11:port
> ii) create an optional attribute wsaw:UsingAddressing/@destination of  
> type xs:anyURI. The value of this attribute, if present, specifies the  
> value of the [destination] property.
>
> 3) Same as (2) but default to the proposal in (1) above.
>
> 4) Allow the wsa:EndpointReference element to be included as the child  
> element of wsdl20:endpoint or the child element of wsdl11:port. When  
> using the wsa:EndpointReference in an wsdl20:endpoint/wsdl11:port the  
> usual WS-Addressing/binding rules apply.
>
> 5) Same as (4) but default to the proposal in (1) above.
>
>
> -Anish
> --
>
> [1]  
> http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr- 
> wsdl.html?content-type=text/html;%20charset=utf-8
> [2]  
> http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr- 
> core.html?content-type=text/html;%20charset=utf-8#msgaddrprops
> [3]  
> http://lists.w3.org/Archives/Public/public-ws-addressing/2005Mar/ 
> 0255.html
>
>
>
>

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Wednesday, 13 April 2005 22:15:57 GMT

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