XSD Viewer
Search…
Limitations
What is not possible currently?
Nested complex types are ignored by the parser for now. Please use top level complex types when you can.
The add-on is currently unable to generate documentation for:
1
<xs:element name="ConfigElement">
2
<xs:complexType>
3
<xs:sequence>
4
<xs:element name="Fragments">
5
<xs:complexType>
6
<xs:sequence>
7
<xs:element minOccurs="0" name="ProtocolFragments"/>
8
<xs:element minOccurs="0" name="MailFragments"/>
9
</xs:sequence>
10
</xs:complexType>
11
</xs:element>
12
<xs:element name="Profiles"/>
13
</xs:sequence>
14
</xs:complexType>
15
</xs:element>
Copied!
This is handled correctly:
1
<xs:complexType name="ConfigComplex">
2
<xs:sequence>
3
<xs:element name="Fragments">
4
<xs:complexType>
5
<xs:sequence>
6
<xs:element minOccurs="0" name="ProtocolFragments"/>
7
<xs:element minOccurs="0" name="MailFragments"/>
8
</xs:sequence>
9
</xs:complexType>
10
</xs:element>
11
<xs:element name="Profiles"/>
12
</xs:sequence>
13
</xs:complexType>
14
15
<xs:element name="Complex" type="ConfigComplex"/>
Copied!
Do not hesitate to contact us if this is an issue for you.
Copy link