[
https://issues.apache.org/jira/browse/JCR-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650910#action_12650910
]
Stefan Guggisberg commented on JCR-1880:
----------------------------------------
this is almost certainly caused by yet-another CachingHierarchyManager problem
related to same-name-siblings ;)
there's probably no risk of data corruption, the bug just results in
inconsistent paths reported by the session.
we've identified and fixed quite a few in the past.
> Same name sibling: Jackrabbit behaves differently when calling Node.getPath()
> -----------------------------------------------------------------------------
>
> Key: JCR-1880
> URL: https://issues.apache.org/jira/browse/JCR-1880
> Project: Jackrabbit
> Issue Type: Bug
> Reporter: Thomas Mueller
> Priority: Minor
>
> The following test case behaves differently when calling Node.getPath()
> versus not calling it:
> void test(boolean index) throws Exception {
> FileUtils.deleteDirectory(new File("repository"));
> Repository rep = new TransientRepository();
> Session session = rep.login(new SimpleCredentials("", new char[0]));
> Node test = session.getRootNode().addNode("test");
> Node a = test.addNode("a");
> Node b = a.addNode("b");
> session.save();
> session.move("/test/a/b", "/test/a");
> if (index) {
> b.getPath();
> }
> session.move("/test/a", "/test/a");
> System.out.println("a: " + a.getPath());
> System.out.println("b: " + b.getPath());
> session.logout();
> }
> test(true) prints:
> a: /test/a[2]
> b: /test/a
> test(false) prints:
> a: /test/a
> b: /test/a
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
