Book a Demo

Author Topic: XML Schema imports in build 907  (Read 4409 times)

wdchilders

  • EA Novice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
XML Schema imports in build 907
« on: June 18, 2011, 12:31:21 am »
When I import an XML Schema, many of the elements within a type are lost.  Often 60 to 90% of the elements are missing.  The missing elements are always members of an <all> group, but only some of the elements in the group are dropped and there is nothing to distinguish them from the ones that make it. Below is one such type:
      <xsd:complexType name="TechnologyCatalogType">
            <xsd:annotation>
                  <xsd:documentation>
                        Technology_Catalog table.
                        This table is split into two building blocks.  Either this table type can be used as a building
                        block or the two types above can be used in order to split it.  This table doesn't really require
                        such a split, but it was done as an example.  The query would be done based on the table,
                        but the response form would use one or both of the building block types above.
                  </xsd:documentation>
            </xsd:annotation>
            <xsd:all>
                  <xsd:element name="TechCatId" type="msgns:PKIdType"/>
                  <xsd:element name="SourceId" type="msgns:PKIdType" nillable="true" minOccurs="0"/>
                  <xsd:element name="ITProductClassifierId" type="msgns:PKIdType" nillable="true" minOccurs="0"/>
                  <xsd:element name="HdwSfwStd" type="msgns:HdwSfwStdType" nillable="true" minOccurs="0"/>
                  <xsd:element name="TechnologyName" type="msgns:LongTextType"/>
                  <xsd:element name="Version" type="msgns:ShortTextType" nillable="true" minOccurs="0"/>
                  <xsd:element name="Edition" type="msgns:LongTextType" nillable="true" minOccurs="0"/>
                  <xsd:element name="Platform" type="msgns:ShortTextType" nillable="true" minOccurs="0"/>
                  <xsd:element name="ShortNote" type="msgns:LongTextType" nillable="true" minOccurs="0"/>
                  <xsd:element name="LongNote" type="xsd:normalizedString" nillable="true" minOccurs="0"/>
                  <xsd:element name="VendorSKU" type="msgns:ShortTextType" nillable="true" minOccurs="0"/>
                  <xsd:element name="HCSCEndOfLifeDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="HCSCGeneralAvailabilityDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="HCSCRemoveDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="HCSCPilotDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="HCSCLimitedDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="SourceEndOfLifeDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="SourceGeneralAvailabilityDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="SourceEndOfSupportDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="SourceEndOfSalesDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="SourceEndOfExtendedDt" type="xsd:date" nillable="true" minOccurs="0"/>
                  <xsd:element name="TechCatOwnerId" type="msgns:PKIdType" nillable="true" minOccurs="0"/>
                  <xsd:element name="AuditTrail" type="msgns:AuditTrailType" minOccurs="0"/>
            </xsd:all>
      </xsd:complexType>
« Last Edit: June 18, 2011, 12:31:49 am by wdchilders »
Bill Childers

Very often, people confuse simple with simplistic. The nuance is lost on most.
-   Clement Mok

wdchilders

  • EA Novice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: XML Schema imports in build 907
« Reply #1 on: June 18, 2011, 01:34:46 am »
I have noticed a discriminator between the elements from the <all> group that are imported and those that are dropped.  All the elements that survive the import are of types native to XML Schema. The dropped elements are all of types defined within the schema being imported.  Those type definitions are found in lines below where the dropped elements are.  This does not happen with elements of these same types when they are not part of an <all> group.
Bill Childers

Very often, people confuse simple with simplistic. The nuance is lost on most.
-   Clement Mok