Configuration priority during startup

[Ex-membre de la communauté]

Hi All,

I'm facing an mismatching behavior in AEM 5.6.1/6.0 with documentation. In docs, there is a next priority of configs (https://docs.adobe.com/docs/en/cq/5-6-1/deploying/configuring_osgi.html)

Resolution Order at Startup

The following order of precedence is used:

1. Repository nodes with type sling:OsgiConfig under /apps/*/config....
2. Repository nodes with type sling:OsgiConfig under /libs/*/config....
3. Any .config files from <cq-installation-dir>/crx-quickstart/launchpad/config/.... on the local file system.

So a generic configuration in /libs can be masked by a project specific configuration in /apps.

However, when I created a node with name org.apache.sling.commons.log.LogManager and type sling:OsgiConfig and added the property

org.apache.sling.commons.log.level=info

and in launchpad\config\org\apache\sling\commons\log\LogManager.config I have:

org.apache.sling.commons.log.level="error"

I see that level for LogManager is "Error" instance was rebooted.

It gets more important for me because it was a question about configuration priority on AEM Developer Certification.

[smacdonald2008 · Accepted solution]

Here is an AEM community article that talks about this subject and may be helpful:

http://www.wemblog.com/2012/10/how-to-work-with-configurations-in-cq.html

In this article - order of precedence of selecting a configuration is,

1) /apps
2) /libs
3) File system

[Ex-membre de la communauté]

Thank you Scott,

The article is really helpful! However it looks like file system configuration has the highest priority during startup.

I'm just wondering what will be a correct answer on AEM Developer Cert Exam? That was a question about precedence of configs. I suppose that I have to follow real behavior rather then documentation. Am I?

I'm also thinking about sending an issue regarding documentation. Where is the best place to report it?