[Bug 4127] Proposed WSDL 1.1 element identifiers can not deal with operation name overloading

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4127

           Summary: Proposed WSDL 1.1 element identifiers can not deal with
                    operation name overloading
           Product: WS-Policy
           Version: LC
          Platform: Macintosh
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WSDL1.1-Element-Identifiers
        AssignedTo: fsasaki@w3.org
        ReportedBy: fabian.ritzmann@sun.com
         QAContact: public-ws-policy-qa@w3.org


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.

Received on Tuesday, 2 January 2007 13:32:34 UTC