[
https://issues.apache.org/jira/browse/SLING-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5770.
-----------------------------------
Resolution: Fixed
sling mocks 1.x: rev. 1751928
sling mocks 2.x: rev. 1751927
i implemented a new "SlingContextBuilder" class which allows more fine-grained
control over initializing the context for each class:
* resourceResolverFactoryActivatorProps: pass in a custom set of configuration
property for resource resolver factory acitvator
* callback methods for beforeSetUp, afterSetUp, beforeTearDown, afterTearDown
> 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)
