Annotations in XSD Generation: Problem

[Christian.Hinken]

Hello there,

when generating the XSD element for the reference another Element, EA creates an inner ComplexType. Example:

<xs:element name="...">
<xs:complexType>
<xs:sequence>
<xs:element ref="..." minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:annotation>
<xs:documentation>...</xs:documentation>
</xs:annotation>
</xs:element>


The annotation-element is generated at the wrong place: it should be generated inside the element with the reference. At the current position, it creates an invalid xsd.

Can anyone help me with this problem?

Thanks in advance,

      Christian.

[Egbert]

Hi Christian,

I saw your question to be relevant to problems we experience.

We are building a reference model in EA and we struggle to generate the right XSD for the model.  We would like to import the XSD model into a tool like Altova Mapforce to do mapping between our reference model and various other system meta models.

We found that Altova ask for a "root element" and if you select any of the classes (as a root element) it only import the XSD for the root and his directly associated classes.  The rest of the model is ignored.

I don't know much about namespaces but could this be the problem?

Many Thanks,

Egbert