[
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610064#comment-13610064
]
Mike Müller commented on SLING-2698:
------------------------------------
That's exactly the question: Is it a fully decoupled feature or a feature of
Sling. I notice that some would have it as far away from Sling as possible, but
not me - and I think it's not for Sling's sake. If we implement the feature as
I proposed in the related thread, the resource resolver bundle would become a
depency to the new resourceaccesssecurity bundle, which is in my POV not
correct. Furthermore I prefer to decouple the API from the implementation.
> resource access security service for resource providers without backing ACLs
> ----------------------------------------------------------------------------
>
> Key: SLING-2698
> URL: https://issues.apache.org/jira/browse/SLING-2698
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Mike Müller
> Assignee: Mike Müller
> Fix For: Resource Resolver 1.1.0
>
> Attachments: resource-resolver-wrapper.patch
>
>
> Adding a minmal resource access gate as discussed in [1].
> First step is to define the API interface and a minimal implementation which
> allows to define READ access (rest of CRUD can follow later)
> [1] http://markmail.org/thread/4ctczoiy533tquyl
--
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
