[
https://issues.apache.org/jira/browse/SLING-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050362#comment-17050362
]
Stefan Seifert commented on SLING-9076:
---------------------------------------
ConfigurationResourceResolvingStrategy is part of the SPI and not inteded to be
used by code that just wants to resolve some configurations. it's only to be
used by custom implementations of ConfigurationResourceResolvingStrategy and is
used only by the impl of caconfig.
it still did not understand you initial problem - why is it a problem that you
need to fetch some configurations even before caconfig and all it's services
are fully started? maybe you can change you code that the configuration is
resolved not on startup, but when you need it? after all, the configuration
resolved with caconfig is part of the content, and can change form call to call
at runtime. so it's not a good idea to read a value a startup and keep it.
> 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)
