Book a Demo

Author Topic: Problem with xml schema generation  (Read 3224 times)

ChristianLO

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Problem with xml schema generation
« on: March 04, 2011, 08:29:18 pm »
Dear all,

we have an existing EA model which consists of several packages. Some of the packages are used for xml schema generation. Generated schemas are delivered to different customers. The EA model was created using EA 7.5, schema creation was done with the same version. I’m using EA 7.5.850.

We have to do some adaption, so as a first step I’m trying to reproduce the existing schema via code generation to ensure that we’re not introducing some unintended changes.
However, the newly created schema looks a little different from the original:
Old schema contains elementFormDefault="unqualified" and attributeFormDefault="unqualified“ declaration, which is omitted in new schema.
New schema contains minOccurs="1" maxOccurs="1 declarations, which was omitted in old schema.
I know that these declarations are default values, it should be possible to add/omit them without any effect. However, our customers are not so technology aware and very afraid of unintended changes. So I would like to generate the schema exactly the same way as it was before.
We added a tagged value of elementFormDefault="unqualified" to modify the UML-Profile for one package, but to no avail. Interestingly, a tagged value elementFormDefault="qualified" works, i.e. the attribute is contained in the generated schema. I looked at “Code generation” and “Transformation Templates” but found no clue.
Anyone has an idea?
External adaption via XSLT is the last choice we would like to go for.

Thanks
Christian