[
https://issues.apache.org/jira/browse/OAK-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571367#comment-13571367
]
Michael Dürig commented on OAK-607:
-----------------------------------
This change in behaviour was introduced in OAK-391 as discussed on the list [1]
and as documented by {{CompatibilityIssuesTest}} [2].
[1] http://markmail.org/message/b6dcyae362akyogd
[2]
https://fisheye6.atlassian.com/viewrep/jackrabbit/oak/trunk/oak-jcr/src/test/java/org/apache/jackrabbit/oak/jcr/CompatibilityIssuesTest.java?r1=1374270&r2=1404646
> 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
