You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/05/23 18:10:22 UTC

[jira] [Commented] (OAK-842) Incorrect interaction of orderable child nodes with access control

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

Marcel Reutegger commented on OAK-842:
--------------------------------------

bq. TreeImpl.remove doesn't (can't) update the child order property if the parent is not accessible.

Doesn't removing a child node require write access to the parent node? At least, that's what I think is the case in Jackrabbit 2.x.
                
> Incorrect interaction of orderable child nodes with access control 
> -------------------------------------------------------------------
>
>                 Key: OAK-842
>                 URL: https://issues.apache.org/jira/browse/OAK-842
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Michael Dürig
>
> Working on OAK-813 revealed problems with the interaction of the current implementation of orderable nodes and access control:
> * {{TreeImpl#getOrderedChildNames}} returns all child names regardless whether they are accessible in the current session or not. This might cause errors further down the line like exposure of the existence of child nodes.
> * {{TreeImpl.remove}} doesn't (can't) update the child order property if the parent is not accessible. 

--
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