DO NOT REPLY [Bug 22646] New: - Problem with derived beans in ?wsdl of deployed web service

[bu...@apache.org]

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=22646>.
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=22646

Problem with derived beans in ?wsdl of deployed web service

           Summary: Problem with derived beans in ?wsdl of deployed web
                    service
           Product: Axis
           Version: 1.1
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: lcarreon@towertechnology.com.au


We developed a Java web service based on the WSDL file of an RPC style .NET web 
service.  Some of the methods of the web service contains arguments and return 
values which use class derivation and naturally the Java beans generated by 
WSDL2Java reflect this case.  However, when we implemented the web service we 
didn't use the skeleton or implementation classes generated by WSDL2Java but 
instead used an EJB (session bean) because we have proven that an EJB 
implementation has better performance compared to the skeleton or 
implementation classes from WSDL2Java.  The problem we have is when the web 
service is deployed and view it's dynamic WSDL thru ?wsdl, the elements of 
derived types are missing although the elements of their parent types do exist.