[OAK-3541] VersionableState.copy doesn't respect OPV flag in the subtree

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.3.9, 1.4
• Component/s: core, jcr
• Labels: versioning
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 22/Oct/15 14:40
• Updated: 02/Mar/16 14:47
• Resolved: 26/Oct/15 14:33

Description

while testing my work in OAK-1268 and OAK-2008, i found that items with OPV IGNORE are being copied into the frozen node of a versionable node upon checkin and only the first level child nodes are being tested for the OPV flag.

IMHO the OPV flag should be respected for all items in the subtree and act accordingly. The current bug might prevent versionable child nodes from being properly versioned and will copy items that are expected to be ignored (e.g. access control content) into the version store.

if i am not mistaken the properties are actually tested for the their OPV flag... if that is true, we might even have a bigger issue as the content in the version store is no longer complete and valid (e.g. mandatory/protected/autocreated properties being ignored but the node still being copied over and thus being invalid)

Issue Links

• blocks: OAK-1268 Add support for composite authorization setup
• is related to: OAK-3551 Failing version restore tests