[JCR-3840] NodeTypeDefDiff does not take same-name child type definitions into account

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.1, 2.6.6, 2.8.1
• Assignee: Unico Hommes
• Reporter: Unico Hommes
• Created: 10/Dec/14 13:01
• Updated: 22/Aug/15 14:41
• Resolved: 10/Dec/14 13:49

Description

The following is a legal cnd, accepted both by jackrabbit, and not prohibited by the JCR spec:

[type]
+ child (type1)
+ child (type2)

This scenario is not taken into account by NodeTypeDefDiff, which leads to node types wrongly failing to reload or wrongly succeeding to reload, depending on the situation.

Issue Links

• relates to: JCR-3902 NodeTypeDefDiff incorrectly handles multiple residual property definitions