[JCR-3600] Error adding a new child definition to a nodeType with the same name but different requiredPrimareTypeNames using API

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6.1
• Component/s: jackrabbit-spi-commons
• Assignee: Unassigned
• Reporter: Luca Tagliani
• Created: 24/May/13 08:47
• Updated: 24/May/13 10:26

Description

I want to register a new child definition under an existing nodetype.
This nodetype has yet a child definition with the same name but different requiredPrimaryTypeName.

The NodeTypeDefDiff identify this modification as MAJOR.

This happens because the code of buildChildNodeDefDiffs method use a QNodeDefinitionId constructor that only uses the declaringNodeType and name (that obviously are the same for the two child definitions).

So, when the algorithm test the difference between the old child definitions and the new child definitions finds that the existing child definition is modified (currently the requiredPrimaryNodeType).