Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Date: 20 Jun 2002 11:59:14 -0000
Message-ID: <20020620115914.51.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: axis-dev@xml.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 10058] New:  -
    WSDL2Java should not fail on valid schema

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

WSDL2Java should not fail on valid schema

           Summary: WSDL2Java should not fail on valid schema
           Product: Axis
           Version: future (enh)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: gdaniels@macromedia.com


When Axis WSDL2Java encounters schema constructs/types from the 2001 schema 
spec which it does not understand, it fails (typically crash & burn).  Tom is 
already working on recognizing all the defined schema data types and giving 
a "type not supported" error for types we don't deal with, which is more 
comprehensible than "type referenced but not defined".

For schema constructs we don't understand, like xsd:group, xsd:list, 
xsd:choice, we may want to map the XML to a SOAPElement instead.  This would 
allow the tool to function on valid schemas, giving the user a workable, if 
not easy-to-use, data binding.

So:

<xsd:complexType name="Foo">
  <xsd:choice>...</xsd:choice>
</xsd:complexType>
<xsd:complexType name="Bean">
  <xsd:element name="fooField" type="Foo"/>
</xsd:complexType>

would generate a "Bean" like this:

class Bean {
  public SOAPElement fooField;
  ...
}