jackrabbit-oak-dev mailing list archives

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

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

angela commented on OAK-212:

i don't know how common this is as a use case but i am concerned about breaking backwards
compatibility in this respect because this was something that cannot be fixed once
the oak-api is finalized.

as discussed offline i can live with the property *status* being undetermined or not perfectly
reliable in these cases but looking at the current code i have the impression that this not
only affects the status of the property but also

- access a single property (OAK-220, OAK-218)
- retrieving the path of a property (OAK-226)
- retrieving the parent of a property (OAK-214)

imo these issues all fall back to the fact that oak-api mandates that a property is
only accessed from the parent node and that parent node is accessible if the property is.
> 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