[
https://issues.apache.org/jira/browse/OAK-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501884#comment-13501884
]
angela commented on OAK-460:
----------------------------
yes we need to worry about this a long as we don't have any other way
to determine the protected status of a given node than by accessing
the item definition... this is currently just added on top of JCR
API which will not work in the long run... in other words i think that
we need the ability to determine the characteristics of an item
on a deeper level that JCR... this is not limited to the protection
status. even internal calls that make decisions based on node type
characteristics just use JCR API to retrieve the corresponding
properties. this will not work once we have access control restrictions
being enforced.
> 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
