You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2007/05/29 18:38:16 UTC

[jira] Commented: (JCR-950) The move method doesn't remove the source node

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

Stefan Guggisberg commented on JCR-950:
---------------------------------------

seems to be an o.a,j.core.CachingHierarchyManager issue which seems to be getting out of sync/corrupted somehow.

note that Workspace.move() does work correctly. it's the current session's view which is inconsistent.

> 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: Stefan Guggisberg
>         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.