Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0FD859ECF for ; Fri, 29 Jun 2012 10:57:46 +0000 (UTC) Received: (qmail 6374 invoked by uid 500); 29 Jun 2012 10:57:45 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 6320 invoked by uid 500); 29 Jun 2012 10:57:45 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 6287 invoked by uid 99); 29 Jun 2012 10:57:44 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jun 2012 10:57:44 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id BAB3D141BDA for ; Fri, 29 Jun 2012 10:57:43 +0000 (UTC) Date: Fri, 29 Jun 2012 10:57:43 +0000 (UTC) From: "Felix Meschberger (JIRA)" To: dev@jackrabbit.apache.org Message-ID: <843521000.71117.1340967463767.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1333587519.34216.1340204505023.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (JCR-3350) Easy-to-use utility class for adding ACEs to nodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403828#comment-13403828 ] Felix Meschberger commented on JCR-3350: ---------------------------------------- Some comments: * I would wrap the RepositoryException inside a generic RuntimeException. This makes handling unduly hard and inside a Jackrabbit class, it is probably appropriate to have RepositoryExceptions thrown. But those should be documented * Is it required to check for the existence of the item first ? In other words, would setting the ACL fail if the item would not exist ? What if the item is a property ? * I would get rid of the autoSave flag and just document this method does not save or rollback at all. > Easy-to-use utility class for adding ACEs to nodes > -------------------------------------------------- > > Key: JCR-3350 > URL: https://issues.apache.org/jira/browse/JCR-3350 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-jcr-commons > Reporter: Jeff Young > Assignee: angela > Labels: newbie, patch > Attachments: AccessControlUtils.java, JCR-3350_-_Easy-to-use_utility_class_for_adding_ACEs_to_nodes.patch > > > There should be any easy (one-line) method for adding an ACE to a node in a repo supporting resource-based ACLs. -- 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