[
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605348#comment-13605348
]
Alexander Klimetschek commented on SLING-2698:
----------------------------------------------
IMHO, both the ResourceAccessSecurity interface and the AccessSecurityException
should not be in the sling api but in the separate bundle as well. There is
nothing in the sling API that makes use of it and more importantly, it exposes
them as some kind of application level API, while they are really meant as
"internal" services for resource provider implementations.
> 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
