Java2WSDL currently generates mangled operation names when it encounters
overloaded java names.
I don't think your problem is entirely limited to the name attribute on the
input/output parts.
Russell and I will revisit the overloading question...including
roundtripping...after the beta release.
Thanks,
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
robert woodley
<amenttuat@yahoo. To: [EMAIL PROTECTED]
com> cc:
Subject: Re: overloaded methods
03/15/2002 03:46
PM
Please respond to
axis-user
Thanks for your suggestion. I studied the test cases,
and it seems to me that there is a bug or something in
Java2wsdl. (Though since I'm new to this, the error is
quite possibly mine.)
Basically you can't do a round-trip with overloaded
methods from java->wsdl->java.
I examined the WSDL generated by java2wsdl. on the
<input> and <output> tags in the <operation> element,
there is no 'name' attribute generated. This causes
the over-loaded functions not to be generated
correctly.
The 'name' attribute is used in your test case, which
made me think of it. The WSDL spec (section 2.4.5)
indicates that it is optional and can be
auto-generated. it also states that it only needs to
be unique WITHIN an operation, but in WSDL2Java, it
appears to need to be unique across all operations
within a portType.
This WSDL will work:
<wsdl:portType name="TestCase">
<wsdl:operation name="fcn" parameterOrder="in0">
<wsdl:input name="x" message="intf:fcnRequest"/>
<wsdl:output name="x" message="intf:fcnResponse"/>
</wsdl:operation>
<wsdl:operation name="fcn">
<wsdl:input name="y" message="intf:fcnRequest1"/>
<wsdl:output name="y" message="intf:fcnResponse1"/>
</wsdl:operation>
</wsdl:portType>
This WSDL will NOT work:
<wsdl:portType name="TestCase">
<wsdl:operation name="fcn" parameterOrder="in0">
<wsdl:input name="x" message="intf:fcnRequest"/>
<wsdl:output name="y" message="intf:fcnResponse"/>
</wsdl:operation>
<wsdl:operation name="fcn">
<wsdl:input name="x" message="intf:fcnRequest1"/>
<wsdl:output name="y" message="intf:fcnResponse1"/>
</wsdl:operation>
</wsdl:portType>
And of course this won't work:
<wsdl:portType name="TestCase">
<wsdl:operation name="fcn" parameterOrder="in0">
<wsdl:input message="intf:fcnRequest"/>
<wsdl:output message="intf:fcnResponse"/>
</wsdl:operation>
<wsdl:operation name="fcn">
<wsdl:input message="intf:fcnRequest1"/>
<wsdl:output message="intf:fcnResponse1"/>
</wsdl:operation>
</wsdl:portType>
Thanks for all of your help,
Bob Woodley
--- Russell Butek <[EMAIL PROTECTED]> wrote:
> Overloaded methods work. See the test
> xml-axis/java/test/wsdl/clash/. We
> haven't done any major stress testing on overloaded
> methods, so it wouldn't
> surprise me if there are still holes, but the
> concept is there and it seems
> to work OK.
>
> Russell Butek
> [EMAIL PROTECTED]
>
>
> robert woodley <[EMAIL PROTECTED]> on 03/15/2002
> 12:18:22 PM
>
> Please respond to [EMAIL PROTECTED]
>
> To: [EMAIL PROTECTED]
> cc:
> Subject: overloaded methods
>
>
>
> This pertains to stub generation.
>
> I've seen earlier posts here that indicate that
> there
> was a bug with over-loaded methods. That is, the
> stub
> generator will generate identical signatures, rather
> than the different, overloaded signatures.
>
> Is there a resolution in sight? Any clever
> workarounds
> other than changing the function name?
>
> Thank you,
> Bob Woodley
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Sports - live college hoops coverage
> http://sports.yahoo.com/
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/
