[XERCESC-1952] Different validation results for different empty element syntax: <e xsi:nil="true" /> vs. <e xsi:nil="true"></e>

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.1.3, 3.1.4
• Fix Version/s: 4.0.0
• Component/s: Validating Parser (XML Schema)
• Environment: Windows Vista
• Assignee: Unassigned
• Reporter: Alexey Miroshnichenko
• Created: 30/Nov/10 19:54
• Updated: 01/Dec/21 13:19

Description

In case of <e xsi:nil="true"></e> syntax for empty element used, XSD validation reports follow message

Message: element 'subitem' is nil and must be empty

In case empty element defined as <e xsi:nil="true" /> there is no validation error.

XML file:
===
<?xml version="1.0"?>
<note xmlns="http://www.test"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.test note.xsd">
<item>
<subitem>
<A>text1</A>
<e xsi:nil="true"></e>
<C>text2</C>
</subitem>
</item>
</note>
===

XSD file:
===
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.test"
elementFormDefault="qualified"
targetNamespace="http://www.test">

<xs:element name="note">
<xs:complexType>
<xs:sequence>
<xs:element name="item">
<xs:complexType>
<xs:sequence>
<xs:element name="subitem" nillable="true" type="xs:anyType" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

</xs:schema>
===

Issue Links

• is duplicated by: XERCESC-2232 xsi:nil="false" fails validation for child elements
• is related to: XERCESC-1944 If an element is nil, child elements of this elements do not trigger a validation error
• is related to: XERCESC-2232 xsi:nil="false" fails validation for child elements