Hi, looking at various documentations on the different approaches and the implementations, there seem to be totally different opinions about if merging of resources (and therefore resources) should be done.
For this topic, let's not discuss names or how the resolving really should work, let's focus on one topic: merging. Let's assume you have a global config at: /config/global/foo - with properties @a, @b and a content aware one at: /config/mysite/foo - with properties @b, @c A content resource now sets /config/mysite as its context. If you get the "foo" configuration, do we merge the properties and the result will have @a, @b, and @c? Or is it just @b and @c? I personally think we should *not* support any merging because as soon as you support merging you will need additional ways of not merging properties etc etc. I think a configuration should be the full set of properties. The confmgr implementation works exactly this way as well. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
