[
https://issues.apache.org/jira/browse/OAK-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889462#comment-13889462
]
angela commented on OAK-710:
----------------------------
given the fact that some move operations cannot be detected (e.g. second move
replacing the node of the first move) and that the resulting permission
evaluation is in most cases more restrictive, i decided to leave the failing
tests as known issues (all marked with @Ignore("OAK-710") and updated the
documentation at
http://jackrabbit.apache.org/oak/docs/differences_permission.html.
> PermissionValidator: Proper permission evaluation for moving/renaming nodes
> ---------------------------------------------------------------------------
>
> Key: OAK-710
> URL: https://issues.apache.org/jira/browse/OAK-710
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: angela
> Assignee: angela
> Fix For: 0.16
>
> Attachments: OAK-710.patch
>
>
> In jr-core renaming just requires MODIFY_CHILD_NODE_COLLECTION permission;
> move requires modification of the child collection plus remove + add of the
> target node.
> However, the Validator interface currently doesn't allow for easy detection
> of move/rename operations. For backwards compatibility it was desirable
> to find a solution for this open issue.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
