I'm looking at the 2nd problem. I'll let y'all know what I find out.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: WSDL2Java Bug?
"Cohan, Sean" wrote:
> 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?
This looks like what I reported Saturday morning, and Saturday afternoon I
filled out the bug report.
Right now just don't use --implClass and it should work fine, until this gets
fixed.
It appears to happen when a non basic input parameter is used. If you use
string, int, it works fine, but if you use int[] or some bean then it has a
failure. This is from what I could tell in my experimenting with it. I haven't
looked in the code to see where it is happening, or why.
