axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11492] New: - WSDL2java does not produce correct code for polymophic methods, fundamental bug
Date Tue, 06 Aug 2002 10:51:18 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11492>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11492

WSDL2java does not produce correct code  for polymophic methods, fundamental bug

           Summary: WSDL2java does not produce correct code  for polymophic
                    methods, fundamental bug
           Product: Axis
           Version: beta-3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: ncjudge@hotmail.com


If I have a bean with the following overloaded signitures:-

public interface SomeBeanServiceRules extends java.io.Serializable {
...

  public String getSomething(final String Id)
		throws java.rmi.RemoteException, ServiceException;

  public String getSomething(final String Id, final Timestamp datetime)
		throws java.rmi.RemoteException, ServiceException;
..
}

Then, java2wsdl produces correctly the following WSDL

...

  <wsdl:message name="getSomethingRequestRequest">
  <wsdl:part name="in0" type="SOAP-ENC:string" /> 
  </wsdl:message>
  <wsdl:message name="getSomethingRequest1">
  <wsdl:part name="in0" type="SOAP-ENC:string" /> 
  <wsdl:part name="in1" type="tns1:Timestamp" /> 
  </wsdl:message>
  <wsdl:message name="getSomethingResponse">
  <wsdl:part name="return" type="SOAP-ENC:string" /> 
  </wsdl:message>
  <wsdl:message name="getSomethingResponse1">
  <wsdl:part name="return" type="SOAP-ENC:string" /> 
  </wsdl:message>

...
  <wsdl:operation name="getSomething" parameterOrder="in0">
  <wsdl:input message="intf:getSomethingRequest" /> 
  <wsdl:output message="intf:getSomethingResponse" /> 
  <wsdl:fault message="intf:ServiceException" name="ServiceException" /> 
  </wsdl:operation>
  <wsdl:operation name="getSomething" parameterOrder="in0 in1">
  <wsdl:input message="intf:getSomethingRequest1" /> 
  <wsdl:output message="intf:getSomethingResponse1" /> 
  <wsdl:fault message="intf:ServiceException" name="ServiceException" /> 
  </wsdl:operation>

...

wsdl2java produces the following incorrect stubs, the signatures look up is not 
working in the generator, blah blah ..


public interface SomeBeanServiceRules extends java.rmi.Remote {
    public java.lang.String getSomething(java.lang.String in0, java.lang.String 
in1) throws java.rmi.RemoteException, ServiceException;
    public java.lang.String getSomething(java.lang.String in0, java.lang.String 
in1) throws java.rmi.RemoteException, ServiceException;
 
...
}

I do not believe I am doing anything wrong in tool invocation, etc, but clearly 
this is a fundamental requirement to handle overloading like this.

Mime
View raw message