So why isn't Axis adding the "name" attribute to the <wsdl:input> and
<wsdl:output> when it auto-generates the WSDL? Moreover, I know this worked
before using alpha3. Can I force Axis to do that somehow?
<wsdl:portType name="LavaServiceProxy">
<wsdl:operation name="getRawAddressData" parameterOrder="tn">
<wsdl:input message="intf:getRawAddressDataRequest" />
<wsdl:output message="intf:getRawAddressDataResponse" />
<wsdl:fault message="intf:Exception" name="Exception" />
</wsdl:operation>
<wsdl:operation name="getRawAddressData" parameterOrder="tn notCached">
<wsdl:input message="intf:getRawAddressDataRequest1" />
<wsdl:output message="intf:getRawAddressDataResponse1" />
<wsdl:fault message="intf:Exception" name="Exception" />
</wsdl:operation>
</wsdl:portType>
-----Original Message-----
From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 12:29 PM
To: [EMAIL PROTECTED]
Subject: RE: Same method names, different parameters
You need to match your operation to your portType using the name attribute
so Axis can figure the mapping:
Have a look a the attached wsdl.
Sylvain.
-----Original Message-----
From: Lasker, Kory [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 1:19 PM
To: '[EMAIL PROTECTED]'
Subject: Same method names, different parameters
I have a WSDL that I give WSDL2Java from beta1 to generate client stubs.
Unfortunately, the code it generates cannot be compiled without manual
editing by myself because duplicate function calls are generated.
The web service itself has two methods named getRawAddressData(String tn)
and getRawAddressData(String tn, Boolean bool). The generated code makes
the *ServiceProxy.java class, the skeleton, and the implementation classes
use a duplicate of the two-parameter form of these classes:
getRawAddressData(String tn, Boolean bool). Anyone have any idea why? I'm
attaching the WSDL so you can try it.
Thanks,
Kory Lasker
