jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-950) The move method doesn't remove the source node
Date Wed, 30 May 2007 15:22:15 GMT

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

Dominique Pfister resolved JCR-950.
-----------------------------------

    Resolution: Fixed

There was some bad assumption in the PathMap (located in jackrabbit-jcr-commons): after moving
/node1 to /result, the CachingHierarchyManager determined that its internal representation
of the root tnode had become invalid and therefore told its PathMap to remove it. The PathMap
has some check to prevent the root node from being completely removed, but unfortunately forgot
to remove its children and associated object, which left an orphaned "node1" child in the
root node's children map.

Fixed in revision 542838.

> The move method doesn't remove the source node
> ----------------------------------------------
>
>                 Key: JCR-950
>                 URL: https://issues.apache.org/jira/browse/JCR-950
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.3
>            Reporter: Christophe Lombart
>            Assignee: Dominique Pfister
>         Attachments: MoveTest.java
>
>
> Here is a small unit test that demonstrate that the method move doesn't remove the source
node. 

-- 
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