[
https://issues.apache.org/jira/browse/OAK-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562684#comment-13562684
]
Alex Parvulescu commented on OAK-343:
-------------------------------------
Interesting, I was looking at a different test :)
For FindAuthorizablesTest#testFindAuthorizableByAddedProperty it seemes like
the diff doesn't go deep enough.
The node hierarchy looks like
{code}
rep:security
/rep:authorizables
/rep:groups
/t
/te
/testPrincipal_4e6b704e <-- with the jcr:uuid I'm interested in
/testGroup_1c22a39f
{code}
And everything under /rep:groups is new content that apparently doesn't get
picked up by the diff at all.
> Session.getNodeByUUID requires save call
> ----------------------------------------
>
> Key: OAK-343
> URL: https://issues.apache.org/jira/browse/OAK-343
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr
> Reporter: angela
> Assignee: Thomas Mueller
> Attachments: oak-343-QueryIndex.patch, OAK-343-v2.patch
>
>
> while adding mix:referenceable to a new node immediately assigns a
> uuid and makes the node referenceable, session.getNodeByUUID only works
> after saving the changes.
> the following test illustrates this behavior:
> @Test
> public void getNodeByUUID() throws RepositoryException {
> Node node = getNode("/foo").addNode("boo");
> node.addMixin(JcrConstants.MIX_REFERENCEABLE);
> assertTrue(node.isNodeType(JcrConstants.MIX_REFERENCEABLE));
> String uuid = node.getUUID();
> assertNotNull(uuid);
> assertEquals(uuid, node.getIdentifier());
> Node nAgain = node.getSession().getNodeByUUID(uuid);
> assertTrue(nAgain.isSame(node));
> assertTrue(nAgain.isSame(node.getSession().getNodeByIdentifier(uuid)));
> }
--
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
