You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2015/02/19 13:57:11 UTC

[jira] [Created] (SLING-4437) MockJcrResourceResolverFactory should allow to register services dynamically.

Tomek Rękawek created SLING-4437:
------------------------------------

             Summary: MockJcrResourceResolverFactory should allow to register services dynamically.
                 Key: SLING-4437
                 URL: https://issues.apache.org/jira/browse/SLING-4437
             Project: Sling
          Issue Type: Improvement
            Reporter: Tomek Rękawek
             Fix For: Testing Sling Mock 1.1.4


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)