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-165) NodeDelegate should not use Tree.getChild() but rather Root.getTree()
Date Wed, 04 Jul 2012 13:59:33 GMT

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

Jukka Zitting commented on OAK-165:

I understand where this is coming from (access control), but I'm concerned that as a result
we now have to repeatedly resolve the full path every time we want to access something. In
practice all the relevant information will already be cached in memory, so it may not be that
much of a problem, but we're still adding path parsing and resolution steps to a place where
they wouldn't really be necessary.
> NodeDelegate should not use Tree.getChild() but rather Root.getTree()
> ---------------------------------------------------------------------
>                 Key: OAK-165
>                 URL: https://issues.apache.org/jira/browse/OAK-165
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>         Environment: {{Tree.getChild()}} is problematic wrt. to access control. {{Root.getTree()}}
should be used instead. 
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>             Fix For: 0.4

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