Menu

#6 All xsd elements were not generated

open
None
5
2007-05-07
2007-03-27
Howard
No

I have a rather complex schema we are working with.

We have a XSD file just for our datatypes, however when I ran Dingo against the xsd, it did not generate a class for every element defined in the XSD.

I have yet to find the pattern of what was ignored. Some elements are <simpleType> and some were <complexType>, however, other elements were generated.

In the XSD snippet below, uomSpeed and valSpeed are generated classes. valSpeed inherits valSpeedBase, however valSpeedBase is not generated.

================%<=================
<schema xmlns:aixm="http://www.aixm.aero/schema/5.0" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml" xmlns:xlink="http://www.w3.org/1999/xlink" targetNamespace="http://www.aixm.aero/schema/5.0" elementFormDefault="unqualified" attributeFormDefault="unqualified" version="5.0 RC1">
<annotation>
<appinfo source="urn:eurocontrol:specification:aixm:schema:xsd:AIXM-DataTypes.xsd:5.0 RC1">AIXM-DataTypes.xsd</appinfo>
</annotation>
<!-- ... Other elements here ... -->
<simpleType name="uomSpeed">
<annotation>
<documentation></documentation>
</annotation>
<restriction base="xsd:string">
<enumeration value="KM/H">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
<enumeration value="KT">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
<enumeration value="MACH">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
<enumeration value="M/MIN">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
<enumeration value="FT/MIN">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
<enumeration value="M/SEC">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
<enumeration value="FT/SEC">
<annotation>
<documentation></documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>

<!-- ... Other elements here ... -->

<simpleType name="valSpeedBase">
<annotation>
<documentation></documentation>
</annotation>
<restriction base="xsd:decimal">
<pattern value="\d{1,8}(\.\d{1,2}){0,1}"></pattern>
</restriction>
</simpleType>

<complexType name="valSpeed">
<simpleContent>
<annotation>
<documentation></documentation>
</annotation>
<extension base="aixm:valSpeedBase">
<attribute name="uom" type="aixm:uomSpeed" use="required"></attribute>
</extension>
</simpleContent>
</complexType>

<!-- ... Other elements here ... -->

</schema>
================%<=================

Discussion

  • Peter Lin

    Peter Lin - 2007-04-26

    Logged In: YES
    user_id=220288
    Originator: NO

    the latest release now handles relative import/includes correctly
    peter

     
  • Peter Lin

    Peter Lin - 2007-04-26
    • status: open --> closed-fixed
     
  • Howard

    Howard - 2007-05-07

    Logged In: YES
    user_id=1754269
    Originator: YES

    I tested this with the latest code and it still does not work correctly.
    The class valSpeedBase is not generated.

    I think it may have gotten closed with the resolution of a different issue.

     
  • Howard

    Howard - 2007-05-07
    • assigned_to: nobody --> woolfel
    • status: closed-fixed --> open
     
  • Peter Lin

    Peter Lin - 2007-05-07

    Logged In: YES
    user_id=220288
    Originator: NO

    I'll take a look tomorrow.

    peter

     

Log in to post a comment.