[
https://issues.apache.org/jira/browse/OAK-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640458#comment-13640458
]
angela commented on OAK-794:
----------------------------
one more thing i only realized when applying the patch:
IMO the compareTo method on the PermissionEntry will not work properly. in only
takes the path into
consideration but ignores the index... that was one reason for having the key
:-)
let's take a look at that as well....
> 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
>
>
> 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
