[
https://issues.apache.org/jira/browse/SLING-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443425#comment-13443425
]
Felix Meschberger commented on SLING-2579:
------------------------------------------
To clarify Carsten's idea:
* ResourceResolverFactory DS component is not defined as a service.
* The ResourceProvider[Factory] references are optional/multiple (0..n) and of
course dynamic.
* The ResourceResolverFactory component is configured with an optional list of
service PIDs (or filters against the service registration properties).
* The ResourceResolverFactory registers itself as a service once all filter
requirements are met
* The ResourceResolverFactory unregisters itself as a service as soon as one or
more filter requirements are not met (any longer).
Unfortunately target filters cannot be used in the manner we want to setup the
requirements.
> ResourceResolverFactory should only be available if specific
> ResourceProvider/Factories are registered
> ------------------------------------------------------------------------------------------------------
>
> Key: SLING-2579
> URL: https://issues.apache.org/jira/browse/SLING-2579
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.0.0
>
>
> The ResourceResolverFactory should only be available if a configurable set of
> providers is available-
> We should add a string array property whose value can either be a pid or a
> filter expression (starting with a '(')
> Only if for all configured values a matching provder/factory is available a
> RRFactory will be registered
--
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
