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 Sedding (JIRA)" <ji...@apache.org> on 2016/02/23 10:38:18 UTC

[jira] [Comment Edited] (OAK-4037) AccessControlValidator: include paths in AccessControlExceptions

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

Julian Sedding edited comment on OAK-4037 at 2/23/16 9:37 AM:
--------------------------------------------------------------

Attached is a [proposed patch|^OAK-4037.jsedding.patch].


was (Author: jsedding):
Attached is a proposed patch.

> AccessControlValidator: include paths in AccessControlExceptions
> ----------------------------------------------------------------
>
>                 Key: OAK-4037
>                 URL: https://issues.apache.org/jira/browse/OAK-4037
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.3.16
>            Reporter: Julian Sedding
>            Assignee: angela
>            Priority: Minor
>
> I had a situation where a system was throwing exceptions about duplicate ACEs during installation of multiple nested content packages.
> It was rather difficult to identify the culprit of the issue, because the exception's message does not contain any paths.
> It would be nice to have paths in the exceptions thrown by {{AccessControlValidator}} to make analysis of such issues easier.



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