[
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593324#comment-13593324
]
Carsten Ziegeler commented on SLING-2698:
-----------------------------------------
I'm not sure if I like the idea of a general customizer :) this opens the door
to everyone to easily replace a resource resolver with some own implementation.
I still like the wrapping idea though :)
However, thinking about it, I'm not sure if wrapping the resolver is a better
solution than wrapping the resource with a decorator - the adaption mechanism
would still be based on the real underlying resource, so we might end up in the
same situation.
I think in the end it boils down to the question, whether we want to add the
implementation to the resource resolver bundle - or if we want to have it
separate. As soon as we do the second we open doors we can't close later on. As
the default setup has no impact, I would rather pay the price of adding the
code to the resource resolver bundle than having a cleaner code separation with
the price of open doors.
> Add a minimal resource access gate
> ----------------------------------
>
> 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
