Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 19 Jul 2012 08:23:34 +0000 (UTC)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: <1774539574.74923.1342686214827.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <721440085.18174.1334251998432.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OAK-64) Privilege Management
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jukka Zitting commented on OAK-64:
----------------------------------

bq. i would appreciate if you would at least state that your implementation is just a quick hack

That's what I meant to do with my comment above. There are also TODOs in the code on properly handling persistence of changes and things like updating jcr:all.

The reason why I opted for the bare minimum change for now is that I didn't want to start making more significant modifications while you were on vacation. If you have suggestions on how and where registered privileges should be persisted, I'd be happy to spend some time implementing them.
                
> Privilege Management
> --------------------
>
>                 Key: OAK-64
>                 URL: https://issues.apache.org/jira/browse/OAK-64
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, jcr
>            Reporter: angela
>            Assignee: angela
>
> implement privilege management such as defined by jackrabbit API

--
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