[JCR-1128] XML import always throws ItemExistsException when trying to overwrite existing nodes

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
• Fix Version/s: 1.3.3
• Component/s: JCR API
• Assignee: Stefan Guggisberg
• Reporter: Honwai Wong
• Created: 13/Sep/07 13:23
• Updated: 19/Aug/21 09:53
• Resolved: 13/Sep/07 14:44

Description

According to the JCR-API, it should be possible to govern the import of XML serialized referenceable nodes in case of UUID collision. Unfortunately, the UUID conflict is handled too late during import, an ItemExistsException is always thrown beforehand due to not allowed same-name-siblings.

Simply try to import a previously exported referenceable node twice, providing either

• ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING or
• ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING.

This will fail and result in an ItemExistsException.

Issue Links

• is related to: JCR-1512 Incorrect check for replace when importing item with colliding id
• is related to: OAK-9541 ItemExistsException: "Node with the same UUID exists" thrown during SysView import with existing different UUID