200586 - Operation overloading not working properly in WSDL

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Web Services, defect)

Description

[Nisheeth Ranjan]

Steps to reproduce:

1) Go to abiove URL
2) Hit the "Call foo('test')" button
3) See the string "foo(int) called with parameter 0" in the Results textbox.

Expected result:

The string "foo(string) called with parameter test" should show up in the
Results textbox.

The WSDL file (http://webstar.nscp.aoltw.net:8080/ws/overload.wsdl) defines two
functions: foo(int) and foo(string).

The SOAP request sent out when "Call foo('test')" is pressed contains the
<IntArg> element instead of the <StringArg> element.  IntArg and StringArg are
defined in the WSDL file as <part> names in two separate <message> elements.

Comment 1

[harishd]

There are a couple of problems:

1) Since the WSDL loader requests for operation-by-name it ends up processing
only one operation ( i.e., the first operation that matches the name ). I should
be able to fix this.

2) Apparently XPConnect invokes method by name ( ignoring the signature ) and
ends up invoking the first method that mathces the name in question. For this I
need David Bardley's help. CCing him.

Comment 2

[harishd]

Attachment: Patch v1.0 - Part 1

Select operation by index rather than by name.

Comment 3

[David Bradley]

Would it be possible to mangle the method names, much like C++ does?

Comment 4

[Johnny Stenback (:jst)]

Yeah, that'd be one way to do it, and I think we should do that to make it
possible from script to explicitly select which method to call, but I think we
should try to be smart too, when possible.

Comment 5

[m]

There ist no method overloading feature in WebServices/SOAP.
Dont't try to get this working - it will be non standard and will not work with
any Web Servers I know.

Comment 6

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

WSDL is gone from Gecko.