[
https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044457#comment-17044457
]
Julian Sedding commented on SLING-9076:
---------------------------------------
[~nischgup] Stefan's concern that your suggested "solution" is incomplete is
valid regardless of whether AEM implements this interface. Imagine that
tomorrow AEM ships with an extra implementation, then your code would break
again.
BTW, you can already fix this yourself. OSGi DS allows you to specify the
[minimum cardinality of a service via
configuration|https://osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-minimum.cardinality.property].
In addition you could even specify a custom target filter in your
configuration to control which implementations are used.
> CA config resolver API is not returning any resources when invoked on
> instance start
> ------------------------------------------------------------------------------------
>
> Key: SLING-9076
> URL: https://issues.apache.org/jira/browse/SLING-9076
> Project: Sling
> Issue Type: Bug
> Reporter: Nischay Gupta
> Priority: Major
>
> Ca config resolver API is not returning any resources when invoked on bundle
> activate when AEM instance starts – this is because of late binding config
> resolution strategy service.
> In *ConfigurationResourceResolvingStrategyMultiplexerImpl* the cardinality is
> set to atleast one *cardinality=ReferenceCardinality.MULTIPLE* but it should
> be *cardinality=ReferenceCardinality.ATLEAST_ONE*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
