Hi all, I want to use a don't repeat yourself and configuration by exception approach for storing information off thousands very similar node trees in an content repository. e.g.
default configuration (very large tree!): /hello /hello/world /hello/world/a=1 /hello/world/b=2 configuration 1 (only two exceptions): /hello/world/b=3 /hello/world/c=3 from the overlaying/merging of the two trees (default + configuration 1) I will get the resulting /hello /hello/world /hello/world/a=1 /hello/world/b=3 /hello/world/c=3 notice that b=3 because it was overwritten by configuration 1. Is there a mechanism, query to virtually merge to node trees in this additive manner? I still have no clue on how to deal with a configuration 1 wants to delete a path from default. I am completely new to content repositories, so be very kind if the solution is obvious. Hints and ideas are very welcome. Cheers Carsten
