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 16340] New: - Axis 1.1 WSDL checking too strict?
Date Wed, 22 Jan 2003 17:48:49 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=16340>.
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=16340

Axis 1.1 WSDL checking too strict?

           Summary: Axis 1.1 WSDL checking too strict?
           Product: Axis
           Version: 1.1beta
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: jasnell@us.ibm.com


Hmm.. I'm wondering if the WSDL checking in the Axis
org.apache.axis.client.Service initService(...) method is becoming too
strict...

Given the perfectly valid schema (taken from one of IBM's Web Services
Toolkit demos), I'm getting an error [2].  The schema is referenced from a
WSDL file used to initialize a Service object.

In one test, I modified the schema to include an <import namespace="
http://www.w3.org/2000/09/xmldsig#" /> to see if that would clear up the
problem and it does not.

IMHO, Axis should not die if it cannot find a schema definition for a
referenced type that is not part of the targetNamespace.  If Axis cannot
find the definition for the referenced type, then it should treat it as a
generic MessageElement without explicit type information.

Mime
View raw message