sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nischay Gupta <nisch...@adobe.com.INVALID>
Subject Issue in config resolver binding strategy in Ca config resolver API
Date Wed, 19 Feb 2020 15:48:11 GMT
The is a query wrt to Adobe Experience Manager
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 cardinality=ReferenceCardinality.MULTIPLE
so when the Adobe Experience Manager instance starts it is dependent on the resourceResolver
service in Caconfig which in turn depends on resourceResolvingStrategy but since its cardinality
is Multiple it returns null as defaultResourceResolvingStrategy is yet not there but it should
be  cardinality=ReferenceCardinality.ATLEAST_ONE so that ConfigurationResourceResolvingStrategyMultiplexerImpl
waits for atleast defaultResourceResolvingStrategy to set

A bug is also logged for the same
https://issues.apache.org/jira/browse/SLING-9076


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message