[
https://issues.apache.org/jira/browse/OAK-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627780#comment-13627780
]
Michael Dürig edited comment on OAK-766 at 4/17/13 11:49 AM:
-------------------------------------------------------------
I suggest to conceptually solve this in the same way it is done with
{{NodeState}}. That is adding the concept of iterability and existence to
trees. This way you could navigate through a "non existing" tree to a child
tree of a given name.
Implementation wise this means however that we need to adjust node builder
implementations to support this. See OAK-781
was (Author: mduerig):
I suggest to conceptually solve this in the same way it is done with
{{NodeState}}. That is adding the concept of iterability and existence to
trees. This way you could navigate through a "non existing" tree to a child
tree of a given name.
Implementation wise this means however that we need to adjust node builder
implementations to support this.
> TreeImpl#*Location: unable retrieve child location if access to parent is
> denied
> --------------------------------------------------------------------------------
>
> Key: OAK-766
> URL: https://issues.apache.org/jira/browse/OAK-766
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: angela
> Assignee: Michael Dürig
> Attachments: OAK-766-patch.txt
>
>
> as a consequence of OAK-709 we now have an issue with the way
> SessionDelegate and Root#getLocation access a node in the hierarchy
> which has an ancestor which is not accessible.
> specifically RootImpl#getLocation will be served a NullLocation for the
> first ancestor which is not accessible and consequently any accessible
> child node cannot be accessed.
> in order to reproduce the issue you may:
> - change AccessControlConfigurationImpl to use PermissionProviderImpl instead
> of the tmp solution
> - and run o.a.j.oak.jcr.security.authorization.ReadTest#testReadDenied
--
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
