[SLING-4437] MockJcrResourceResolverFactory should allow to register services dynamically.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Testing Sling Mock 1.1.2
• Fix Version/s: Testing Sling Mock 1.2.0
• Component/s: Testing
• Labels: mocks
• Assignee: Unassigned
• Reporter: Tomek Rękawek
• Created: 19/Feb/15 12:56
• Updated: 26/Feb/15 11:48
• Resolved: 19/Feb/15 20:22

Description

The MockJcrResourceResolverFactory class creates it's own mocked OSGi BundleContext and uses it to create a ResourceResolverFactory. Part of the OSGi environment initialization performed in the class is registering OSGi services to be available by the mocked resolver. By default there is only one service - SlingRepository.

However, the more recent versions of ResourceProvider implementations requires other services, eg. PathMapper. Right now there is no way to inject this service into the mocked OSGi container. The MockJcrResourceResolverFactory should allow to register custom services, so it'll be compatible with the future versions of ResourceResolvers and Providers.

Issue Links

• relates to: SLING-848 Support getting versioned resources by using uri path parameters