[ https://issues.apache.org/jira/browse/SLING-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert updated SLING-5770: ---------------------------------- Affects Version/s: Testing Sling Mock 2.0.0 Fix Version/s: Testing Sling Mock 2.0.0 Testing Sling Mock 1.6.4 > Allow to configure resource resolver mapping > -------------------------------------------- > > Key: SLING-5770 > URL: https://issues.apache.org/jira/browse/SLING-5770 > Project: Sling > Issue Type: Improvement > Components: Testing > Affects Versions: Testing Sling Mock 1.6.2, Testing Sling Mock 2.0.0 > Reporter: Konrad Windszus > Assignee: Stefan Seifert > Fix For: Testing Sling Mock 1.6.4, Testing Sling Mock 2.0.0 > > > Currently the {{ResourceResolverFactoryActivator}} being registered in > https://github.com/apache/sling/blob/trunk/testing/mocks/sling-mock/src/main/java/org/apache/sling/testing/mock/sling/ResourceResolverFactoryInitializer.java#L123 > is not configured at all. > Since resource resolver mapping is a topic which is often implemented in the > wrong way, it should be possible to setup some mapping for SlingContext to > allow to test in a more realistic way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)