[
https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045522#comment-17045522
]
Nischay Gupta edited comment on SLING-9076 at 2/26/20 1:41 PM:
---------------------------------------------------------------
[~jsedding] [~sseifert]
I ll explain the scenario
We have our AEM bundle which is dependent on *ConfigurationResourceResolver*
which is inturn dependent on service *ConfigurationResourceResolvingStrategy*
whose cardinality is *MULTIPLE, we require Default implementation of*
*ConfigurationResourceResolvingStrategy which returns null as the service is
not up when AEM instance starts*
**
So it is a case of transitive dependency, how can we then achieve our goal to
resolve this transitive dependency
Also since I can also use *ConfigurationResourceResolvingStrategy directly*
Is there any difference between the resource we get from using
*ConfigurationResourceResolvingStrategy or* *ConfigurationResourceResolver***
was (Author: nischgup):
[~jsedding] [~sseifert]
I ll explain the scenario
We have our AEM bundle which is dependent on *ConfigurationResourceResolver*
which is inturn dependent on service *ConfigurationResourceResolvingStrategy*
whose cardinality is *MULTIPLE, we also require Default implementation of*
*ConfigurationResourceResolvingStrategy which returns null as the service is
not up when AEM instance starts*
**
So it is a case of transitive dependency, how can we then achieve our goal to
resolve this transitive dependency
Also since I can also use *ConfigurationResourceResolvingStrategy directly*
Is there any difference between the resource we get from using
*ConfigurationResourceResolvingStrategy or* *ConfigurationResourceResolver***
> 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)
