[JCR-1880] Same name sibling: Jackrabbit behaves differently when calling Node.getPath()

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4, 1.5, 2.6
• Fix Version/s: 2.6.5, 2.7.2
• Component/s: jackrabbit-core
• Assignee: Unico Hommes
• Reporter: Thomas Mueller
• Created: 25/Nov/08 13:23
• Updated: 08/Nov/13 16:46
• Resolved: 16/Oct/13 14:02

Description

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