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

["Tomek Rękawek (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomek Rękawek updated SLING-4437:
---------------------------------
    Attachment: SLING-4437.patch

Patch proposal attached.

> 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
>
>         Attachments: SLING-4437.patch
>
>
> 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)