[
https://issues.apache.org/jira/browse/OAK-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567492#comment-13567492
]
Michael Dürig commented on OAK-598:
-----------------------------------
Ack. Let's remove {{TreeLocation.NULL}} from the API and make it an internal
implementation class only and let's add a method {{exists()}} to
{{TreeLocation}}, which can be used to test whether an item at that location
exists/is accessible.
> 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
>
> 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
