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-271) IMPORT_UUID_COLLISION_REPLACE_EXISTING removes the existing node + subtree
Date Wed, 16 Nov 2005 17:32:30 GMT
     [ http://issues.apache.org/jira/browse/JCR-271?page=all ]
     
Stefan Guggisberg resolved JCR-271:
-----------------------------------

    Resolution: Invalid

not a bug, works as spec'ed.

quoting javadoc of  Session#importXML:

IMPORT_UUID_COLLISION_REPLACE_EXISTING: If an incoming referenceable node has the same UUID
as a node already existing in the workspace, then the already-existing node is replaced by
the incoming node in the same position as the existing node. 

'replacing' a node means removing the existing node (which of course includes its children)
and adding the new node (incl. its children) at the same location.

> IMPORT_UUID_COLLISION_REPLACE_EXISTING removes the existing node + subtree
> --------------------------------------------------------------------------
>
>          Key: JCR-271
>          URL: http://issues.apache.org/jira/browse/JCR-271
>      Project: Jackrabbit
>         Type: Bug
>     Reporter: scharles

>
> If you try to import a node in between existing hierarchy using IMPORT_UUID_COLLISION_REPLACE_EXISTING
it removes the sub tree instead of only replacing the imported node.
> To reproduse - 
> 1. create /main/sub
> 2. export /main/sub
> 3. add nodes under /main/sub/...
> 4. Session.importXML(.., .., IMPORT_UUID_COLLISION_REPLACE_EXISTING);
> You will left with /main/sub only

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message