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 "angela (JIRA)" <ji...@apache.org> on 2019/04/26 13:52:00 UTC

[jira] [Updated] (OAK-8284) Improvements to EntryPredicate

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

angela updated OAK-8284:
------------------------
    Attachment: EntryPredicate.patch

> Improvements to EntryPredicate
> ------------------------------
>
>                 Key: OAK-8284
>                 URL: https://issues.apache.org/jira/browse/OAK-8284
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, security
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>         Attachments: EntryPredicate.patch
>
>
> [~stillalex], while working on overall coverage of the permission evaluation code base i found  {{org.apache.jackrabbit.oak.security.authorization.permission.EntryPredicate}} confusing and hard to understand. attached patch contains an attempt to simplify and improve this class central to permission evaluation by completely separating the 3 major cases: 
> - evaluation for repository level (no path, no tree), 
> - evaluation based on a non-null path and finally 
> - evaluation based on a non-null tree object and an optional property. 
> feedback welcome.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)