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

Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2011/02/09 19:01:57 UTC

[jira] Updated: (JCR-2883) Node.orderBefore and JackrabbitNode.rename should check for ability to modify children-collection on parent node

     [ https://issues.apache.org/jira/browse/JCR-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela updated JCR-2883:
------------------------

      Component/s: security
                   jackrabbit-core
    Fix Version/s: 2.3.0

> Node.orderBefore and JackrabbitNode.rename should check for ability to modify children-collection on parent node
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-2883
>                 URL: https://issues.apache.org/jira/browse/JCR-2883
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, security
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> currently the implementation of Node.orderBefore and JackrabbitNode.rename perform the same validation that is executed
> for a move operation which includes removal of the original node. however, the methods mentioned above only include
> a manipulation on the child-node-collection of the parent (subset of the current check). therefore the permission check should be 
> adjusted accordingly.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira