Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3 rc1
-
Fix Version/s: 1.3
-
Component/s: XML code generator
-
Labels:None
-
Testcase included:yes
-
Number of attachments :
Description
When creating an element type instead of adding properties directly in the element so that the type can be reused there are problems for NMTOKENS. For example, the Details element from below does not get generated in the same package and location as DetailsIn. This does not happen if the restricted type is something else like int, string, etc.
<xs:complexType> <xs:sequence> <xs:element name="DetailsOut" type="fsd:DetailType"></xs:element> <xs:element name="DetailsIn"> <xs:simpleType> <xs:restriction base="xs:NMTOKENS"> <xs:enumeration value="ZERO"></xs:enumeration> <xs:enumeration value="ONE"></xs:enumeration> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> <xs:simpleType name="DetailType"> <xs:restriction base="xs:NMTOKENS"> <xs:enumeration value="TWO"></xs:enumeration> <xs:enumeration value="THREE"></xs:enumeration> </xs:restriction> </xs:simpleType>
I'm trying to research if there are specific properties I have to enable for these enumerations to work with nmtokens, and what happens if I make a list of them. Any other tips would be greatly appreciated!