[AXIS-154] WSDL2Java should not fail on valid schema

• Type: Bug
• Status: Open
• Resolution: Unresolved
• Component/s: WSDL processing
• Environment: Operating System: Other; Platform: Other
• Bugzilla Id: 10058
• Assignee: Unassigned
• Reporter: Glen Daniels
• Created: 20/Jun/02 18:59
• Updated: 11/Jan/12 11:43

Description

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;
...
}