Hi,
while comparing Adobe's confmgr with our CA configurations, there is one
difference with inheritance handling.
In Sling there is no way to specify to not inherit a configuration if
inheritance is enabled, e.g.
/conf/foo/sling:configs/a
/b
/conf/foo/subproject/sling:configs/c
+sling:configCollectionInherit=true
If you now have the use case, that you want a list of "a" and "c" for a
context resource pointing to "/conf/foo/subproject" there is no way to
handle this wit CA configurations.
On the other hand confmgr uses a very subtle approach:
you can create a node at /conf/foo/subproject/sling:configs/b with no
jcr:content sub node and this will block inheritance for "b". It also
means that as soon as you use inheritance, you have to use jcr:content
sub nodes. So in the example above at least "c" needs to have one.
I think this mechanism is too much magic to add it to CA configs,
however it would be great to have some hook or SPI on dealing with it
through the CA implementation.
So far I couldn't come up with any good apprach. Anyone have an idea?
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
