You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/02/20 07:50:00 UTC
[jira] [Updated] (SLING-9076) CA config resolver API is not
returning any resources when invoked on instance start
[ https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-9076:
---------------------------------------
Summary: CA config resolver API is not returning any resources when invoked on instance start (was: CA config resolver API is not returning any resources when invoked on instance start(Adobe Experience Manager))
> 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)