... if you have merging (or inheritance) then you change the attribute of a parent and this influences all childs and you have no idea what happens there...
We can create a felix console plugin that shows for a given context path and config name the value of the property and the path from where it was taken - that way both developers and ops can quickly check what's going wrong if results are unexpected.
I personally think this comes all down to tooling ...
So this could mean e.g. an additional maven plugin, which handles merging of configurations and then the runtime can work without merging. The problem I see with that is that * you end up having two similar configuration model types (one in the source code that supports merging and one effective one for the runtime) - this makes the mechanism harder to understand for everyone * the tooling has to be created and IMHO it'll not be easier/less code than creating a smarter runtime (even if we take into account that we have to create the felix console plugin to make it traceable) Regards Georg
