jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1128) XML import always throws ItemExistsException when trying to overwrite existing nodes
Date Thu, 13 Sep 2007 14:45:32 GMT

     [ https://issues.apache.org/jira/browse/JCR-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Guggisberg resolved JCR-1128.
------------------------------------

    Resolution: Fixed

fixed in svn r575325

thanks for reporting this issue!

> 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: JCR API
>    Affects Versions: 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
>            Reporter: Honwai Wong
>            Assignee: Stefan Guggisberg
>            Priority: Minor
>             Fix For: 1.4
>
>
> 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.


Mime
View raw message