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 "Antonio Sanso (JIRA)" <ji...@apache.org> on 2013/05/03 14:54:15 UTC

[jira] [Resolved] (OAK-794) CompiledPermissionImpl#getReadStatus wrong ordering

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

Antonio Sanso resolved OAK-794.
-------------------------------

    Resolution: Fixed

This can be closed since the new readstatus structure proposed in OAK-774 solves this issue 
                
> CompiledPermissionImpl#getReadStatus wrong ordering
> ---------------------------------------------------
>
>                 Key: OAK-794
>                 URL: https://issues.apache.org/jira/browse/OAK-794
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Antonio Sanso
>         Attachments: OAK-794-patch.txt, OAK-794-patch.txt
>
>
> CompiledPermissionImpl#getReadStatus  takes in consideration the priority for the userEntry versus the groupEntry.
> The issue is that in case the readStatus has been calculated this priority has been already took in consideration in the CompiledPermissionImpl#buildReadStatus.
> Taking in consideration twice will break the logic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira