[
https://issues.apache.org/jira/browse/SLING-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272514#comment-16272514
]
angela commented on SLING-7227:
-------------------------------
[~bdelacretaz]. can you please take of that? The repo init you invented is
incomplete, which prevents Adobe from using it despite the fact that it was
announced as the preferred way of doing things. Thanks.
cc: [~marett]
> Repo Init: Add ability to register custom privileges
> ----------------------------------------------------
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: angela
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a
> way to register a custom privilege during repo init. I am sure this is an
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract,
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
