[
https://issues.apache.org/jira/browse/OAK-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316258#comment-14316258
]
Chetan Mehrotra commented on OAK-2490:
--------------------------------------
bq. the not so nice thing is the long chain of passing the PermissionProvider
down the stack
Just modifying your current approach you can access the PermissionProvider via
FilterImpl -> SelectorImpl -> QueryImpl -> ExecutionContext ->
PermissionProvider. You can either
# Expose the QueryImpl in SelectorImpl
# Or expose ExecutionContext in QueryImpl and provide a getter for that in
SelectorImpl
Then you would not have to pass around any instance
> Make it possible to use the PermissionProvider from within query indexes
> ------------------------------------------------------------------------
>
> Key: OAK-2490
> URL: https://issues.apache.org/jira/browse/OAK-2490
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.1.7
>
> Attachments: OAK-2490.0.patch, OAK-2490.1.patch
>
>
> As discussed on OAK-2423 and OAK-2473 it's useful to have a
> {{PermissionProvider}} down into {{QueryIndex}} implementations and/or
> {{SelectorImpl}}, depending on wether the ACL checks have to be done on an
> implementation base or generally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
