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

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

Michael Dürig edited comment on OAK-842 at 5/24/13 10:08 PM:
-------------------------------------------------------------

Yes but in order to update the child order in the parent you need a reference to the parent which means you need to read the parent in the first place. 
Note how this is different from deleting the child node in that test case. There a reference to the parent is not involved. 
                
      was (Author: mduerig):
    Yes but in order to update the child order in the parent you need a reference to the parent which means you need to read the parent in the first place. 
                  
> 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