Currently there are two possibilities to configure the resource resolver mapping:
a) Through the OSGi property "resource.resolver.mapping" of the PID org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl b) Through the resources below the path being specified by the OSGI property "resource.resolver.map.location" of the PID org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl Both possibilities are overlapping in certain parts, but some aspects can only be configured in either a) or b). Let me quickly reconsider which way supports which features 1) Different incoming and outgoing mappings can only be given in a) because b) will always assume the mapping is for both directions (except in the case when regular expression are used, as then the entry in b) will only be used for incoming mapping. To only specify an outgoing mapping with b) is impossible) 2) Mapping for a specific Host or Scheme can only be given in b). I opened https://issues.apache.org/jira/browse/SLING-5670 about that! 3) Redirecting for incoming mappings is only supported through b) 3) Reconfiguring through a) is more expensive as this requires a lot of depending OSGi services to be restarted! I have the feeling, that b) is the preferred way from a performance but also from a feature point of view, but it is very sad that b) is lacking the possibility 1. So instead of extending both mechanisms to make them cover the same features, I would like to know what is the recommended approach. Then we can look into how to make the full feature set maintainable through this preferred way of configuring and at the same time deprecate the other. Thanks, Konrad
