[
https://issues.apache.org/jira/browse/SLING-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483073#comment-13483073
]
Ian Boston commented on SLING-2541:
-----------------------------------
Would it be possible to collect all the metadata from all sources into a list
or set and then merge once its all collected, with some indication of where
each item came from?
Also: ResourceProviders have priority if stops priority being based on the
Resource itself. Although it may be more expensive, locating Resources and as
they are found and passing the current best result to the next Provider will
let it decide if its got a better result. If you want to have an impl that
gives the ResourceProvider a fixed priority then it can short circuit that
resolution with a wrapper checks the priority of the provided Resource.
I realise, that might need more Resource API or something out of band (so might
not be good)
> General mechanism to chain resource providers
> ---------------------------------------------
>
> Key: SLING-2541
> URL: https://issues.apache.org/jira/browse/SLING-2541
> Project: Sling
> Issue Type: Bug
> Components: 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
