[jira] [Resolved] (SLING-12352) ContentLoader XML / JSON initialisation should be done in a lazy way (when needed)

["Henry Kuijpers (Jira)" <ji...@apache.org>]

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

Henry Kuijpers resolved SLING-12352.
------------------------------------
      Assignee: Henry Kuijpers
    Resolution: Fixed

> ContentLoader XML / JSON initialisation should be done in a lazy way (when needed)
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-12352
>                 URL: https://issues.apache.org/jira/browse/SLING-12352
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing Sling Mock 3.5.0
>            Reporter: Henry Kuijpers
>            Assignee: Henry Kuijpers
>            Priority: Major
>             Fix For: Testing Sling Mock 3.5.2
>
>
> When calling context.load(), a content loader is created in a lazy way (when it's not there, it is instantiated and otherwise a cached instance is returned).
> However, when instantiating this content loader, everything needed for XML & JSON is set up, regardless of calls to json() or xml() being made or not. This should also be done in a lazy way.
> ----
> A specific issue that can be tackled this way is running parallel tests in combination with XML parsers and their ugly statics, interfering with each other.
> This would tackle the "No page manager." / "No asset manager." errors that can be seen when using AemContext.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)