You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to generate a JSON schema from a sample XSD. All elements were generated successfully to json schema except one element from my XSD schema was generated improperly.
And here is the element copied from input XSD:
<xs:elementname="CONTENT_STATUS_HISTORY">
<xs:annotation>
<xs:documentation>Use this element for listing the document history</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequencemaxOccurs="unbounded">
<xs:elementname="CONTENT_STATUS"type="TYPE_CONTENT_STATUS_STRUCT"/>
<xs:elementname="SUBMISSION_NUMBER"type="submissionnumberType">
<xs:annotation>
<xs:documentation>Submission number for the given Status type</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
+++++++ See the generated jsonschema below ++++++
I do not know why jsonschema_issues.txt
name: 'contentstatusAndSUBMISSIONNUMBER',
Why does it generate a name like this : contentstatusAndSUBMISSIONNUMBER and propertyorder like this contentstatusAndSUBMISSIONNUMBER
propertyInfos: [{
name: 'contentstatusAndSUBMISSIONNUMBER',
required: true,
minOccurs: 2,
collection: true,
elementTypeInfos: [{
elementName: 'CONTENT_STATUS',
typeInfo: '.TYPECONTENTSTATUSSTRUCT'
}, {
elementName: 'SUBMISSION_NUMBER'
}],
type: 'elements'
}]
Because you have an unbounded sequence with two elements. This results in a heterogeneous collection which may contain items of both elements. This is the only way to adequately represent your XML Schema.
Hi!
I tried to generate a JSON schema from a sample XSD. All elements were generated successfully to json schema except one element from my XSD schema was generated improperly.
And here is the element copied from input XSD:
+++++++ See the generated jsonschema below ++++++
I do not know why
jsonschema_issues.txt
name: 'contentstatusAndSUBMISSIONNUMBER',
The text was updated successfully, but these errors were encountered: