might be best explain with an example:
so I have this file in my node tree = /apps/myconfigs/config.publish/com.mycompany.services.myclass.config. I checked configMgr and the values for "com.mycompany.services.myclass" is completely different to the one stored in the file.
I know about runmodes but how does how the the publisher know the the configuration file for the class "com.mycompany.services.myclass" is exactly in this location (/apps/myconfigs/config.publish)?
EDIT: If I edited/saved the values in configMgr for this class and the new config file is saved inside the default location in /apps/system/config
Solved! Go to Solution.
Views
Replies
Total Likes
The following order of precedence applies for OSGI configurations
For run mode specific configurations, multiple run modes can be combined. Configurations in such folders will be applied if all run modes match a run mode defined at startup.
In your case there might be other configuration defined in combination with publish run mode which is taking precedence over config.publish
Hope this will help you to understand the order of precedence for OSGI configs
https://aemcases.blogspot.com/2018/05/osgi-service-configuration-and-its.html?m=1
The following order of precedence applies for OSGI configurations
For run mode specific configurations, multiple run modes can be combined. Configurations in such folders will be applied if all run modes match a run mode defined at startup.
In your case there might be other configuration defined in combination with publish run mode which is taking precedence over config.publish
@jayv25585659 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Views
Replies
Total Likes
Views
Likes
Replies