Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: WSDL2Java Bug?
Forgive my ignorance, but�which input/output clauses - messages, operation, ...�?� I see names for these.� Thanks.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 3:12 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2Java Bug?
The WSDL you showed me was invalid. The input/output clauses DID NOT contain name="..." attributes. They MUST contain name attributes for overloaded operations.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: WSDL2Java Bug?
I was getting valid WSDL, but I wasn't getting valid java when I fed it into WSDL2Java (i.e., the overridden methods were created with the same signature with the Note class as a parameter.)
�
I'm going to reduce some levels of indirection and test it out again.� The original source does not have to be used.�
�
Thanks.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 1:34 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2Java Bug?
I'm not able to reproduce your problem. I get valid WSDL, ie, WSDL that names the input/output clauses. I DID have to change NoteApi, though. I removed "extends Api" since I don't have an Api class. If you still have problems, perhaps you could send me Api.java.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: Russell Butek/Austin/IBM@IBMUS
cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: WSDL2Java Bug?
Here it is.� I will download the nightly build and try it again.� My full download was on 6/26.� I'll let you know.� Here are the commands�I used:
�
C:\My Documents\com\gosps\cbd\note>java org.apache.axis.wsdl.Java2WSDL -o Note.wsdl -l"http://localhost:8080/axis/servic
es/NoteApi" -n "urn:api.note.cbd.gosps.com" -p"com.gosps.cbd.note.api" "urn:api.note.cbd.gosps.com" com.gosps.cbd.note.a
pi.NoteApi
�
C:\My Documents\com\gosps\cbd\note>java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true Note.wsdl
�
�
Thanks.
�
�
�
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 9:09 AM
To: [EMAIL PROTECTED]
Subject: Re: WSDL2Java Bug?
Sean, could you send me your interface and WSDL files? The problem is, you have bad WSDL. When working with overloaded operations, the input/output clauses in the portType must be named so that the binding input/output clauses have a way to distinguish which portType operation they're referring to. I'd like to see the interface so I can figure out why Java2WSDL generated bad WSDL.
Which version of axis are you using? If not a nightly build, could you download a recent nightly build and see whether it still fails?
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: WSDL2Java Bug?
I used Java2WSDL �to gen my wsdl file from my �interface. �I then �used
WSDL2Java to gen my �stubs,skeletons,impls, �etc. �My interface has a �method
with 2 signatures. One passes in a ��class and the other passes in an Integer.
It looks like the wsdl is �correctly created with 2 �messages/operations:
- <wsdl:message �name="getNoteRequest">
<wsdl:part ��name="in0" �type="SOAP-ENC:int"/>
</wsdl:message>
- <wsdl:message ��name="getNoteRequest1">
<wsdl:part name="in0" ��type="intf:Note"/>
</wsdl:message>
.
.
.
- <wsdl:operation name="getNote" ��parameterOrder="in0">
<wsdl:input ��message="intf:getNoteRequest"/>
<wsdl:output ��message="intf:getNoteResponse"/>
</wsdl:operation>
<wsdl:operation �name="getNote" �parameterOrder="in0">
<wsdl:input ��message="intf:getNoteRequest1"/>
<wsdl:output ��message="intf:getNoteResponse1"/>
</wsdl:operation>
However, �the WSDL2Java generated interface incorrectly contains 2 �versions
of the �method each with the �class as it's argument:
public ��com.gosps.cbd.note.api.Note �getNote(com.gosps.cbd.note.api.Note
in0) �throws �java.rmi.RemoteException;
public �com.gosps.cbd.note.api.Note ��getNote(com.gosps.cbd.note.api.Note
in0) �throws �java.rmi.RemoteException;
Is �this a bug in WSDL2Java or am I �missing �something?
Thanks.
Sean ��Cohan
Software Performance �Systems
