Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <17156945.134621292415784019.JavaMail.jira@thor>
Date: Wed, 15 Dec 2010 07:23:04 -0500 (EST)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-2841) Avoid path resolution in case of
 non-wildcard ACEs (follow-up to JCR-2573)
In-Reply-To: <4669186.56651291982281371.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

angela resolved JCR-2841.
-------------------------

    Resolution: Fixed

> Avoid path resolution in case of non-wildcard ACEs (follow-up to JCR-2573)
> --------------------------------------------------------------------------
>
>                 Key: JCR-2841
>                 URL: https://issues.apache.org/jira/browse/JCR-2841
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, security
>    Affects Versions: 2.2.0
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.2.1
>
>
> adding the ability to specify wildcard-ac-entries in the default resource based access control management lead to
> always resolving the id passed to AccessControlProvider#canRead in order to be able to properly evaluate
> any wildcard-aces present.
> this could be improved with minor refactoring that postpones the path resolution and omitting it if there are no
> wildcard-aces to compare with.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.