[
https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040817#comment-17040817
]
Nischay Gupta commented on SLING-9076:
--------------------------------------
[~sseifert] , a quick search in AEM code suggests that AEM relies on the
*default implementation for all its purposes* and does not implement
*ConfigurationResourceResolvingStrategy* and *ConfigurationResourceResolver.*
** So now considering the scenario stated in the bug, can the cardinality be
changed or else how should we achieve our goal? I think it is a genuine use
case where on bundle activate or in some background job, we want to cache some
config resources, but we need to be sure that we are getting the correct ones.
> 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)
