You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/11/05 14:44:12 UTC
[jira] [Resolved] (SLING-2541) General mechanism to chain resource
providers
[ https://issues.apache.org/jira/browse/SLING-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2541.
-------------------------------------
Resolution: Fixed
> General mechanism to chain resource providers
> ---------------------------------------------
>
> Key: SLING-2541
> URL: https://issues.apache.org/jira/browse/SLING-2541
> Project: Sling
> Issue Type: Bug
> Components: API, Extensions, ResourceResolver
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: File System Resource Provider 1.0.4, Extensions Bundleresource 2.0.8, API 2.2.6, Resource Resolver 1.0.0
>
>
> Right now, the bundle resource and the fs resource "hard coded" test for a session and for a node in the repository, if the requested resource is a folder.
> I think we should generalize this and provide a mechanism for a resource provider to get a resource from a resource provider with a lower ranking. This would solve this use case but also allow a use case where a resource provider combines information from different resource providers, e.g. when the repository stores meta information about a file (just a rough thought)
--
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