[OAK-4085] Malformed node type definition when reregistered after upgrade

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.3.10
• Fix Version/s: 1.2.16, 1.4, 1.4.0
• Component/s: core, jcr
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 03/Mar/16 10:59
• Updated: 19/May/16 08:01
• Resolved: 07/Mar/16 08:14

Description

When a node type is reregistered after an upgrade from an earlier release, the resulting node type definition may be malformed. As noted in OAK-3584, the node type representation in content was not compliant with JCR already before. As explained here the situation after an upgrade is even worse: http://markmail.org/message/7kjkqlt3erbocpin

Issue Links

• relates to: OAK-3584 PathNotFoundException when reading child node and property definitions below nt root