jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-212) Move status of property to PropertyState
Date Thu, 02 Aug 2012 08:29:02 GMT

    [ https://issues.apache.org/jira/browse/OAK-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427171#comment-13427171

Jukka Zitting commented on OAK-212:

bq. a property may be accessible even if the parent tree isn't

Is this a real use case, i.e. does anyone use such access control settings in practice? If
not, I think we should explicitly declare that in Oak properties can not be accessed without
access to the containing node.

The rationale is that for simplicity, performance and memory reasons it would be better if
we didn't have to track each property as a standalone object with its own state. Instead it
should be possible to reuse common PropertyState instances like "jcr:primaryType=nt:resource".
> Move status of property to PropertyState
> ----------------------------------------
>                 Key: OAK-212
>                 URL: https://issues.apache.org/jira/browse/OAK-212
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
> Currently the status of a property is retrieved from the parent tree object.
> With access control being enforced a property may be accessible even if the
> parent tree isn't.
> IMO the status should therefore be retrieved from the PropertyState instead
> of calling Tree#getPropertyStatus.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message