WSDL2Java Bug?

[Cohan, Sean]

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