XML import always throws ItemExistsException when trying to overwrite existing
nodes
------------------------------------------------------------------------------------
Key: JCR-1128
URL: https://issues.apache.org/jira/browse/JCR-1128
Project: Jackrabbit
Issue Type: Bug
Components: Jackrabbit API
Reporter: Honwai Wong
Priority: Minor
Fix For: none
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
