[JCRVLT-685] ImportMode REPLACE vs IdConflictPolicy LEGACY vs stashing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.4
• Fix Version/s: 3.7.0
• Component/s: vlt
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 10/Feb/23 18:26
• Updated: 19/Jul/23 13:22
• Resolved: 14/Feb/23 16:19

Description

Consider this case:

• existing node "/tmp/x" in repo with UUID x1 and mixin type xm that requires a child node "/tmp/x/child"
• package import with IdConflictPolicy.LEGACY and ImportMode REPLACE (default). Package contains /tmp/x" with UUID x2 (!= x1) and does not have the mixin type xm, nor the child node required by it

Import detects UUID present in package and on node to be updated, decides to stash it. New node is created, child nodes are moved back from stashed node, but properties are not (due to ImportMode REPLACE), thus the mixin type is not re-added. Import fails.

Either we should restore the mixin type, or we should not restore the child that is only allowed by that mixin type.

(This is a change in behavior introduced by JCRVLT-551)

Issue Links

• is related to: JCRVLT-551 Set jcr:uuid to value from package when updating node
• links to: GitHub Pull Request #274