Using Designer 5.1.2, generated XSD has maxOccurs value as "unbounded" even though the sequence has maxLength(No.of elements in the sequence) set to some value.
Article ID: KB0087114
Updated On:
| Products | Versions |
|---|---|
| TIBCO Designer | - |
| Not Applicable | - |
Description
Resolution:
Symptoms
=========
In the designer 5.1.2 , when you do "Export as XML Schema" you should see maxOccurs same as the maxLength set for the sequence in the generated XSD. Currently XSDs will show "unbounded" as the value.
Impact
======
Data Loss.
Workaround
==========
Edit the .aeschema file in a text editor (like WordPad), and ensure that <maxLength>
always appears before <elementType> within <sequence> elements.
Cause
=====
There are two possible orderings, and only one of them is recognized by the "export as xsds" tool, producing the correct maxOccurs value.
Resolution
=========
This will be addressed in the future release. For details contact support@tibco.com.
Note:-The Numeric occurrence constraints other than 0, 1 or unbounded cause often complex validation and
may even be prohibited in the future by W3C's XMLSchema group. numeric occurrence constraints
other than 0, 1 or unbounded cause often complex validation and may even be prohibited in the future
by W3C's XMLSchema group. Hence the fix will allow at the most 3 occurrences.
Symptoms
=========
In the designer 5.1.2 , when you do "Export as XML Schema" you should see maxOccurs same as the maxLength set for the sequence in the generated XSD. Currently XSDs will show "unbounded" as the value.
Impact
======
Data Loss.
Workaround
==========
Edit the .aeschema file in a text editor (like WordPad), and ensure that <maxLength>
always appears before <elementType> within <sequence> elements.
Cause
=====
There are two possible orderings, and only one of them is recognized by the "export as xsds" tool, producing the correct maxOccurs value.
Resolution
=========
This will be addressed in the future release. For details contact support@tibco.com.
Note:-The Numeric occurrence constraints other than 0, 1 or unbounded cause often complex validation and
may even be prohibited in the future by W3C's XMLSchema group. numeric occurrence constraints
other than 0, 1 or unbounded cause often complex validation and may even be prohibited in the future
by W3C's XMLSchema group. Hence the fix will allow at the most 3 occurrences.
Issue/Introduction
Using Designer 5.1.2, generated XSD has maxOccurs value as "unbounded" even though the sequence has maxLength(No.of elements in the sequence) set to some value.
Feedback
Yes
No
Powered by
