You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2020/02/19 20:41:00 UTC
[jira] [Commented] (SLING-9076) CA config resolver API is not
returning any resources when invoked on instance start(Adobe Experience
Manager)
[ https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040410#comment-17040410 ]
Stefan Seifert commented on SLING-9076:
---------------------------------------
we could change this - but depending on how many services exist that implement ConfigurationResourceResolvingStrategy this will help or will not help.
afaik AEM comes with it's own implementations, and sling caconfig comes with a default implementation, that means we have at least two implementations. setting it to ATLEAST_ONE does not ensure both of them are present.
so it still is possible that the API is not returning the expected resources.
> CA config resolver API is not returning any resources when invoked on instance start(Adobe Experience Manager)
> --------------------------------------------------------------------------------------------------------------
>
> 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)