hello Bertrand. >On Fri, Oct 17, 2014 at 11:56 AM, Stefan Seifert <sseif...@pro-vision.de> >wrote: >> ... https://cwiki.apache.org/confluence/x/1ATTAg ... > >Thanks for this. Looking at your use-cases it feels like your context >is always derived from the current resource's position in the content >tree, am I correct?
yes, this is the configuration scope identified by a configuration id (e.g. the path of the site's root page) >If yes that explains why you suggest putting the configuration >alongside the content - but we might want to also support configs >stored under /conf or somewhere else safe. Quoting Alex K earlier in >this thread > >>> ...configs have a different management lifecycle and ACLs than content ... this is not directly related - storing the config along with the config was just the first persistence provider implemented as example. the configuration id the resource path, but as long if this key is preserved the configuration can be stored anywhere, also below a /conf node. the alternative storing at /conf is already implemented [1] - it's up to the system configuration which persistence provider is used. stefan [1] http://wcm.io/config/core/persistence-providers.html
