[JCR-3635] Manually specified jcr:frozenUuid overwriting the one assigned by the VersionManager when versioning node

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 0.9, 2.4.5, 2.6.4, 2.7.1
• Component/s: versioning
• Assignee: Jukka Zitting
• Reporter: Florin Iordache
• Created: 30/Jul/13 15:35
• Updated: 26/Aug/19 08:47
• Resolved: 01/Aug/13 09:15

Description

Let's assume we have node N with a manually assigned jcr:frozenUuid property (e.g. taken from an existing frozenNode version of another node).

When creating versions of node N, the manually assigned frozenUuid property will overwrite the frozenUuid automatically created by the VersionManager in the versioning process because the jcr:frozenUuid property is not skipped when copying the existing properties from the versioned node to the frozen node in the version subtree.
This can potentially cause issues whenever the jcr:frozenUuid is used in the future, since it would basically point to a different versioned node.