Hi, for a long time we have tried to use sensible defaults for all of our configurations. This allows our users to run a default Sling without any additional configuration (it should even be possible to run it without a Configuration Admin service available - but that's another story).
While we were pretty successful with this, we simply blew it with the move from login administrative to service users. A lot of the (core) modules now use service users and these require a configured mapping in order to work properly. While for example the servlets resolver previously did not require any configuration, it requires at least the mapping. Which in turn means you can't simply use that module as-is. Switching to service users is of course a good idea but I'm wondering if we can find a way to get back to a configurationless Sling again? Clearly we don't want to the mapping to be part of the bundles using the service users. One possible solution would be an out of the box bundle with the necessary repo init and configurations. This would cover the core bundles like servlets resolver and resource resolver. But maybe there is a better option? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
