You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Christophe Lombart (JIRA)" <ji...@apache.org> on 2007/05/28 23:23:15 UTC
[jira] Created: (JCR-950) The move method doesn't remove the source
node
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
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.
[jira] Commented: (JCR-950) The move method doesn't remove the
source node
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (JCR-950) The move method doesn't remove the
source node
Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JCR-950) The move method doesn't remove the source
node
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Lombart updated JCR-950:
-----------------------------------
Attachment: MoveTest.java
> 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
> 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.
[jira] Assigned: (JCR-950) The move method doesn't remove the
source node
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg reassigned JCR-950:
-------------------------------------
Assignee: Dominique Pfister (was: Stefan Guggisberg)
passing on to the CachingHierarchyManager expert ;)
> 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.
[jira] Assigned: (JCR-950) The move method doesn't remove the
source node
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg reassigned JCR-950:
-------------------------------------
Assignee: Stefan Guggisberg
> 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.
[jira] Updated: (JCR-950) The move method doesn't remove the source
node
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-950:
------------------------------
Fix Version/s: 1.3.1
Merged to the 1.3 branch in revision 544239.
> 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
> Fix For: 1.3.1
>
> 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.