[ http://issues.apache.org/jira/browse/AXIS-799?page=all ]
Davanum Srinivas resolved AXIS-799:
-----------------------------------
Assign To: (was: Axis Developers Mailing List)
Resolution: Fixed
i thinks this is fixed now. right glen?
thanks,
dims
> [doc/lit] WS-I problems with WSDL for Document/literal web services
> -------------------------------------------------------------------
>
> Key: AXIS-799
> URL: http://issues.apache.org/jira/browse/AXIS-799
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: 1.1rc2
> Environment: Operating System: Windows XP
> Platform: All
> Reporter: Faisal Waris
> Attachments: ComplexWSDL.zip, EncodingIssue.zip, testfiles.zip
>
> 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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
