[
https://issues.apache.org/jira/browse/JCR-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3880:
------------------------
Attachment: JCR-3880_2.patch
alternative patch based on the feedback provided by [~tripod]: as stated above
i like the idea of reporting about the success of the operation, however, it
would feel more natural to me, to return those IDs that could not be processed.
otherwise the API consumer would have to diff the return value to the original
list of ids or compare the lengths to see if all ids were successfully added.
[~tripod], wdyt?
> Allow to add/remove group members by ID
> ---------------------------------------
>
> Key: JCR-3880
> URL: https://issues.apache.org/jira/browse/JCR-3880
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-api
> Reporter: angela
> Assignee: angela
> Attachments: JCR-3880.patch, JCR-3880_2.patch
>
>
> for some cases it would be convenient if it was possible to add/remove group
> members by ID without having to retrieve the corresponding authorizable
> upfront... in particular for package imports as provided by jackrabbit
> fvault, where the group my be imported before the members are present.
> similar it might be useful to remove dangling membership entries once a
> former member got removed.
> the current implementations already allow for such a behavior when using an
> XML import run with the _besteffort_ flag set for the import of the
> associated protected items (while failing in case of the other
> import-behaviour settings). such it would complete the API coverage for a
> feature we already support while at the same time control it based on the
> repository configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
