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:
<xs:element name="ConfigElement"> <xs:complexType> <xs:sequence> <xs:element name="Fragments"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="ProtocolFragments"/> <xs:element minOccurs="0" name="MailFragments"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Profiles"/> </xs:sequence> </xs:complexType> </xs:element>
This is handled correctly:
<xs:complexType name="ConfigComplex"> <xs:sequence> <xs:element name="Fragments"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="ProtocolFragments"/> <xs:element minOccurs="0" name="MailFragments"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Profiles"/> </xs:sequence> </xs:complexType> <xs:element name="Complex" type="ConfigComplex"/>
Do not hesitate to contact us if this is an issue for you.