DO NOT REPLY [Bug 18714] New: - Axis not generating correct WSDL for Document/literal web services

[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=18714>.
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=18714

Axis not generating correct WSDL for Document/literal web services

           Summary: Axis not generating correct WSDL for Document/literal
                    web services
           Product: Axis
           Version: 1.1rc2
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: fwaris@ford.com


We want to standardize on the WS-I Basic Profile for Web Services implemented 
at our organization. In evaluating Axis 1.1RC2 we found that although by 
design it supports doc/literal web services (a WS-I recommendation), Axis 
either (1) generates WSDL that does not conform to the WS-I Basic Profile or 
(2) does not generate WSDL at all for complex Java code.

I am attaching two Zip'ed files that deal with the two separatae WSDL issues 
listed above:

1)

This zip file contains Java source code, corresponding jar file, and a 
Java2WSDL generated WSDL file. 

This set of files shows that the generated WSDL does not conform to the WS-I 
basic profile recommendations. In particular the Array encoding uses SOAP 
encoding rather than XML Schema.

2)

This zip file contains a complex WSDL. The WSDL is from a .Net Web Service 
returning an Oagis BOD document. Embedded in the WSDL is the complex Schema of 
the Oagis BOD being returned. I took this WSDL and generated "--server-side" 
Java code, service classes and deployment descriptor. I then implemented and 
deployed the service in WAS 4.04. For this service, the automatic WSDL 
generation did not work at all. The ...?wsdl url returned 404 and I did not 
see a stack trace on the console (WAS was running under WSAD).