You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Honwai Wong (JIRA)" <ji...@apache.org> on 2007/09/13 15:24:32 UTC
[jira] Created: (JCR-1128) XML import always throws
ItemExistsException when trying to overwrite existing nodes
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.
[jira] Updated: (JCR-1128) XML import always throws
ItemExistsException when trying to overwrite existing nodes
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1128:
-------------------------------
Fix Version/s: (was: 1.4)
1.3.2
Merged to the 1.3 branch in revision 577696.
> 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.3.2
>
>
> 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.
[jira] Updated: (JCR-1128) XML import always throws
ItemExistsException when trying to overwrite existing nodes
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg updated JCR-1128:
-----------------------------------
Component/s: (was: Jackrabbit API)
JCR API
Fix Version/s: (was: none)
1.4
Assignee: Stefan Guggisberg
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
> 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.
[jira] Resolved: (JCR-1128) XML import always throws
ItemExistsException when trying to overwrite existing nodes
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ 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.