You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/11/10 09:38:00 UTC

[jira] [Updated] (OAK-4362) SyncMBeanImpl.purgeOrphanedUsers swallows sync-error

     [ https://issues.apache.org/jira/browse/OAK-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated OAK-4362:
--------------------------------
    Fix Version/s: 1.6

> SyncMBeanImpl.purgeOrphanedUsers swallows sync-error
> ----------------------------------------------------
>
>                 Key: OAK-4362
>                 URL: https://issues.apache.org/jira/browse/OAK-4362
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: auth-external
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>             Fix For: 1.6, 1.5.2
>
>
> while writing tests for the sync-bean implementation I found that
> SyncMBeanImpl.purgeOrphanedUsers will swallow the information if the sync (i.e. removal) of an individual orphaned user fails with {{SyncException}}.
> IMO it would be better (and consistent) to list the error with a given "ERR" operation code.



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