i've a question about ConfigurationBuilderImpl: why have we currently introduced an implicit "sling:configs" parent node, which is automatically added to the path when resolving a configuration.
example: /content/site1[@sling:config=/config/site1] when i get the configuration named "x" for /content/site1 i get the config from the resource /config/site1/sling:configs/x - instead of /config/site1/x and why is this only done for the ConfigurationResolver, and not for the ConfigurationResourceResolver? stefan