jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-2883) Node.orderBefore and JackrabbitNode.rename should check for ability to modify children-collection on parent node
Date Wed, 16 Nov 2011 14:48:52 GMT

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

Jukka Zitting updated JCR-2883:
-------------------------------

    Fix Version/s: 2.2.10

Merged to the 2.2 branch in revision 1202725.
                
> 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.2.10, 2.3
>
>
> 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.
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

        

Mime
View raw message