jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3933) potential improvements to membership management
Date Thu, 03 Mar 2016 18:34:18 GMT

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

angela commented on OAK-3933:
-----------------------------

one more comment regarding this suggestion: since the addition of {{Group.addMembers(String...)}}
it is depending on the configuration possible to add members that are only created after editing
the membership. in these cases is simply impossible to distinguish between user and group
upon creating the group-member relationship i.e. the prefixing would not work.

> potential improvements to membership management
> -----------------------------------------------
>
>                 Key: OAK-3933
>                 URL: https://issues.apache.org/jira/browse/OAK-3933
>             Project: Jackrabbit Oak
>          Issue Type: Epic
>          Components: core
>            Reporter: Julian Reschke
>            Assignee: angela
>
> Affected methods are
> - Group.isMember(Authorizable)
> - Group.isDeclaredMember(Authorizable)
> - Group.addMember(Authorizable)
> - Group.addMembers(String...)
> - Group.removeMember(Authorizable)
> - Group.removeMembers(String...)
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message