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 2017/04/29 07:26:04 UTC

[jira] [Resolved] (SLING-6812) sling-mock: Lazy initialization of ResourceResolverFactory

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

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

Completed: At revision: 1793172  


> sling-mock: Lazy initialization of ResourceResolverFactory
> ----------------------------------------------------------
>
>                 Key: SLING-6812
>                 URL: https://issues.apache.org/jira/browse/SLING-6812
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Testing Sling Mock 2.2.6
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>              Labels: mocks
>             Fix For: Testing Sling Mock 2.2.8
>
>
> latest version of sling resource resolver implementation do not register the ResourceResolverFactory unless at least one ResourceProvider instance is registered.
> when using ResourceResolverType.NONE this did not work because the ResourceResolverFactory was tried to initialize before starting the unit test. doing this lazily on first acccess solves the problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)