Hi, bear in mind i really want to “customize” as less as possible. Hence in my point of view it’s wrong too to customize the conf path.
However, context aware configuration allows me to use widgets for AEM pages in /content/conf, i can then reuse in component dialogs in my site, and then have a single point of entry for entering the configuration data, and have fallback, e.g: /content/mysite/us/en/mypage/jcr:content/comp@myData which is let say a list of AEM tags, i can configure in comp’s dialog, in case there is nothing it fall backs to /content/conf/us/en/myconf@myData fall backs to /content/conf/global/myconf@myData with that setup i have the two following features for free : - configure a widget for handling myData once, and reuse in all other places, which brings me consistency, - copy / paste / activate / delete / edit /content/conf/* items very quickly. *not* doing so would make me customize / develop things for the two above features. Nicolas > On Dec 16, 2016, at 10:52 AM, Stefan Seifert <[email protected]> wrote: > > 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:[email protected]] >> Sent: Thursday, December 15, 2016 9:38 AM >> To: [email protected] >> 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 >> >
