Book a Demo

Author Topic: UI Problem with XSDElement MaxOccurs  (Read 3053 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
UI Problem with XSDElement MaxOccurs
« on: December 03, 2008, 06:28:01 pm »
There is a UI problem for XSD Elements.  When you reverse engineer an XSD, it will correctly set the maxOccurs:unbounded to MaxOccurs: * for the XSDElement.  Thus the MaxOccurs (Multiplicity Upper Bound) reads * and the Tagged Value maxOccurs reads unbounded.

If you change the MaxOccurs to (say) 6, EA correctly changes the Multiplicity Upper Bound to:6 and the maxOccurs Tagged Value to: 6.

If you change the MaxOccurs back to *, EA incorrectly sets the MaxOccurs (Multiplicity Upper Bound) to: -1 which makes the Tagged Value read -1.  This is incorrect.

Repoprted,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!