- From: Fabian Ritzmann <Fabian.Ritzmann@Sun.COM>
- Date: Tue, 02 Jan 2007 15:35:34 +0200
- To: public-ws-policy@w3.org
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 Tuesday, 2 January 2007 13:35:33 UTC