in my point of view it is wrong to store the config data in /content/conf if the only motivation to do this is the limitation of some tooling. i would recommend to keep the config root of the default strategies at /conf.
what is the purpose of the "AEM content management tools" - edit the configuration? then have a look at the (not yet finished and not yet documented) http://wcm.io/caconfig/editor/ the is also a sample project https://github.com/wcm-io/wcm-io-caconfig/tree/develop/sample-app it allows to create config editor templates in /content/*, but the config data is loaded from and stored in /conf. the editor shows the config data of the context where the page is created. stefan >-----Original Message----- >From: Nicolas Peltier [mailto:npelt...@adobe.com] >Sent: Thursday, December 15, 2016 9:38 AM >To: users@sling.apache.org >Subject: [caconfig] changing config path > >Hi, > >on my project i want to use context aware config, but in order for me to >profit from some AEM content management tools, i would like to move the >root of my configuration to /content/conf. > >I realized it was not possible unless i change config path in configuration >from /conf to /content/conf. Looks to me that this configuration is just >used to *check* that configuration is allowed. > >what is the best: >- changing it to be “/“ (to allow applications using /conf to still work): >i’m not conscious right now of the risk this represents, >- patching default configuration component to accept multiple configuration >paths, >- tweaking AEM tools to work under /conf (aka you shall not use anything >but “/conf”) > >thanks, >Nicolas >
