[
https://issues.apache.org/jira/browse/OAK-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571401#comment-13571401
]
angela commented on OAK-607:
----------------------------
as far as i remember the discussion on the list was about the effect the move
had on the Tree. that doesn't necessarily mean that the Node gets invalid, does
it?
i don't mind if the tree tree gets invalid, but i think we should fix it for
the Node.
> Old path after moving a new node
> --------------------------------
>
> Key: OAK-607
> URL: https://issues.apache.org/jira/browse/OAK-607
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
>
> Renaming or Moving a new Node using Session#move succeeds but the node still
> exposes the old path.
> {code}
> @Test
> public void testMoveNewNode() throws Exception {
> Node node1 = testRootNode.addNode(nodeName1);
> Node node2 = testRootNode.addNode(nodeName2);
> String destPath = node2.getPath() + "/" + nodeName1;
> move(node1.getPath(), destPath, false);
> assertEquals(destPath, node1.getPath());
> superuser.save();
> assertEquals(destPath, node1.getPath());
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
