W3C home > Mailing lists > Public > public-ws-policy@w3.org > January 2007

RE: NEW ISSUE 4127: Proposed WSDL 1.1 element identifiers can not deal with operation name overloading

From: David Orchard <dorchard@bea.com>
Date: Wed, 10 Jan 2007 09:57:12 -0800
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9C02F68349@repbex01.amer.bea.com>
To: "Fabian Ritzmann" <Fabian.Ritzmann@Sun.COM>, <public-ws-policy@w3.org>

Some more comments on this:

Another 2 solutions:
#3: Leave as is and when there is overloading, the first is used.

#4: Leave as is and when there is overloading, say nothing

I think #2 would have to look something like

<input name="foo"/><input name="bar"/>

Would have something like:
wsdl11.portTypeMessageReference(portType/operation/message(
messageName))

Cheers,
Dave

> -----Original Message-----
> From: public-ws-policy-request@w3.org 
> [mailto:public-ws-policy-request@w3.org] On Behalf Of Fabian Ritzmann
> Sent: Tuesday, January 02, 2007 5:36 AM
> To: public-ws-policy@w3.org
> Subject: NEW ISSUE 4127: Proposed WSDL 1.1 element 
> identifiers can not deal with operation name overloading
> 
> 
> This issue resolves action item 175: 
> http://www.w3.org/2005/06/tracker/wspolicy/actions/175
> 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=4127
> 
> Title
> 
> Proposed WSDL 1.1 element identifiers can not deal with 
> operation name overloading
> 
> Description
> 
> Endpoints described with WSDL 1.1 may have several operations 
> with the same name. Operations that have the same name are 
> distinguished through differing input or output elements.
> 
> Justification
> 
> The current WS-Policy proposal for WSDL 1.1 element 
> identifiers is not able to deal with operation name 
> overloading. With the proposed syntax you could only identify 
> one operation of the endpoint randomly and any other 
> operation of the endpoint with the same name would be ignored.
> 
> Target
> 
> WSDL 1.1 Element Identifiers
> 
> Proposal
> 
> We have at least two options to solve this issue:
> 
> 1. Leave the fragment identifiers in section 2 as proposed 
> and add a normative reference and constraint that the WSDL 
> 1.1 element identifiers can only be applied to WSDL documents 
> that comply with the WS-I Basic Profile 1.1. The BP
> 1.1 section 4.5.3 disallows operation name overloading.
> 
> 2. Modify the fragment identifiers for portType operation and 
> binding operation to deal with operation name overloading.
> 
> 
> 
> --
> Fabian Ritzmann
> Sun Microsystems, Inc.
> Stella Business Park             Phone +358-9-525 562 96
> Lars Sonckin kaari 12            Fax   +358-9-525 562 52
> 02600 Espoo                      Email Fabian.Ritzmann@Sun.COM
> Finland
> 
> 
> 
Received on Wednesday, 10 January 2007 17:59:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:45 GMT