The problem is that overloaded operations should have their input and output clauses named so that they can be distinguished. So the generated WSDL is bad.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
cc:
Subject: re: problem with WSDL2Java
Hello,
I am having a problem that confuses me, using WSDL2Java. I have the
second beta version of axis installed. I don't know if this is a bug.
I included three files. makeit.sh is my script to create the stubs.
The source for the stubs is the java file. The WSDL file is created
from the java file.
If you lookup lookupLocation in the wsdl file, the parameters are
wrong, as there is no place where I have two strings as parameters.
The more annoying problem is when I convert the wsdl file to java
files. I end up with only two functions in the
AxisLMSServerSoapBindingStub.java. There should be four functions, they
each have different numbers of parameters, but the two I see are
identical.
- Is there is problem with WSDL2Java handling overloaded methods?
