[
https://issues.apache.org/jira/browse/OAK-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568797#comment-13568797
]
angela commented on OAK-598:
----------------------------
well... i don't think this is a wise move... if you have a given location at
hand that you knew the path
before it's pretty odd that you can't obtain that path any more nor go back to
the last parent that
was accessible. in other words: you just loose one of the purposes of the
treelocation that was to
access a given item with a call/path without having to access every single
intermediate tree/location.
> TreeLocation#NULL allows to reveal the existence of items that are not
> accessible
> ---------------------------------------------------------------------------------
>
> Key: OAK-598
> URL: https://issues.apache.org/jira/browse/OAK-598
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr
> Reporter: angela
> Assignee: Michael Dürig
> Fix For: 0.7
>
>
> the javadoc of TreeLocation#NULL states:
> {quote}
> This {@code TreeLocation} refers to an invalid location in a tree. That is
> to a location where no item resides.
> {quote}
> while api consumers are not allowed to access items they are not allowed
> to read, the NULL location allows to determine if a given item does really
> not exist or was simply not accessible to the editing content session.
> IMO this should be fixed by not exposing the NULL implementation and
> making sure oak-jcr doesn't need it. maybe adding a shortcut method to
> test the underlying item is not null (e.g. exists()).
--
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
