[
https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047510#comment-17047510
]
Nischay Gupta commented on SLING-9076:
--------------------------------------
[~jsedding] [~sseifert]
Configuring an osgi config in AEM that relies on internal (impl) class names
would result in tight coupling between AEM and Sling which is not desirable.
This would result in a fragile flow.
Another way could be to directly call
{code:java}
ConfigurationResourceResolvingStrategy#getResources {code}
(with atleast one cardinality) from my service instead of
{code:java}
ConfigurationResourceResolver#getResource{code}
*.* But I'm not sure whether there is any functionality level differences
between both APIs. Could you please clarify?
> 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)
