[
https://issues.apache.org/jira/browse/OAK-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501889#comment-13501889
]
Jukka Zitting commented on OAK-460:
-----------------------------------
Do you mean internal code in oak-jcr, or the plugins working through oak-core?
The latter should be able to look at the underlying data without access
limitations, while the former could for example just assume that everything's
allowed if type details aren't available (the underlying commit hooks will in
any case correct such assumptions where needed).
> Node#getDefinition and Property#getDefinition depend on the accessibility of
> the parent node
> --------------------------------------------------------------------------------------------
>
> Key: OAK-460
> URL: https://issues.apache.org/jira/browse/OAK-460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
>
> currently the definition of a given item is obtained by reading the
> node type information of the parent node and is thus relying on the
> accessibility of the parent node. as discussed previously in other
> occasions we cannot rely on this as access to the parent might be
> denied.
> in the long run we may want to think about a way on how to determine
> the definition (or parts of the definition such as for example
> information about the protection status) in the absence of the parent.
--
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
