[ 
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610070#comment-13610070
 ] 

Alexander Klimetschek commented on SLING-2698:
----------------------------------------------

The new resource resolver feature is a separate thing still discussed and we 
are discussimg the sling api bundle, not the resource resolver bundle here. 
Also, you can create a separate API bundle if you want - putting everything 
that is an exported package in Sling into the Sling API is a bad thing. 
Clearly, the Sling API bundle is for all the things that Sling applications 
need. It should not contain Sling "internal" APIs such as this. A servlet/JSP 
or application-level service or component would never have to use this API - 
for them, this would all be transparent behind the resource API.

The goal should really be that if someone does not want this feature, it is not 
exposed. In our case we use only the JCR backend, and have customers/partners 
extending the system - for the reasons discussed, we don't want them to use 
this API at all, so there should be a clear option to not ship it (e.g. that 
separate bundle).
                
> 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

Reply via email to