You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/05/17 15:25:00 UTC

[jira] [Resolved] (SLING-4721) sling-mock: Fully support ResourceResolverFactoryActivator for jcr-mock

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

Stefan Seifert resolved SLING-4721.
-----------------------------------
    Resolution: Fixed

Completed: At revision: 1679854  

the ResourceResolverFactoryActivator is now registered properlay in osgi-mock, additionaly dependencies required by it are registered as well if not already present in bundle context

> sling-mock: Fully support ResourceResolverFactoryActivator for jcr-mock
> -----------------------------------------------------------------------
>
>                 Key: SLING-4721
>                 URL: https://issues.apache.org/jira/browse/SLING-4721
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Testing Sling Mock 1.2.0
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>              Labels: mocks
>             Fix For: Testing Sling Mock 1.2.2
>
>
> in sling-mock 1.2.0 only a stripped down version of ResourceResolverFactoryActivator was used which only supported a single JCR resource provider with the underlying jcr-mock.
> this prohibits the usage (and testing) of custom resource providers because they are not detected when registered in osgi-mock.



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