nilable status is ignored in subsequent declarations of the same element in a
type
----------------------------------------------------------------------------------
Key: XERCESC-1810
URL: https://issues.apache.org/jira/browse/XERCESC-1810
Project: Xerces-C++
Issue Type: Bug
Components: Validating Parser (XML Schema)
Affects Versions: 2.8.0
Reporter: Boris Kolpackov
Copy from the mailing list report. Schema fragment:
<xs:element name="people" nillable="true" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:choice>
<xs:sequence minOccurs="0">
<xs:element name="ID" type="xs:string"/>
<xs:element name="Name" type="xs:string"/>
<xs:element name="Description" type="xs:string"
minOccurs="0"/>
<xs:element name="isAvailable" type="xs:boolean"/>
</xs:sequence>
<xs:sequence minOccurs="0">
<xs:element name="Name" type="xs:string" minOccurs="0"/>
<xs:element name="Description" type="xs:string"
nillable="true" minOccurs="0"/>
</xs:sequence>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
XML fragment:
<people>
<Name>fd</Name>
<Description xsi:nil="true"/>
</people>
The validation failes, the reason is "Message: xsi:nil must not be specified
for the element Description with nillable equals false"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
