[
https://issues.apache.org/jira/browse/SLING-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442385#comment-13442385
]
Konrad Windszus commented on SLING-2579:
----------------------------------------
Isn't it easier to leverage the target attribute for that (OSGi Compendium
112.3.4)? That way you could annotate one ResourceResolverFactory field with
the reference annotation carrying a target attribute and dedicate that field a
special bind method. If you make that reference use the static reference
policy, that component will not be activated, until this factory is available.
To me that looks much simpler, than to extract everything into a separate
Activator component.
> 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
