[
https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046786#comment-17046786
]
Stefan Seifert commented on SLING-9076:
---------------------------------------
still it can lead to unexpected results as soon as multiple implementations of
the ConfigurationResourceResolvingStrategy are deployed in the system (even if
currently only the default is present). once another bundle adds an additional
implementation you do not know which of them fulfills the "1 minimum".
maybe you are looking for something like a "system ready" event, although in a
modular OSGi-based system it's difficult to say when the system is ready.
> 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)
