[ https://issues.apache.org/jira/browse/SLING-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855832#comment-17855832 ]
Stefan Seifert commented on SLING-12352: ---------------------------------------- looks good to me > 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 > Priority: Major > > 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)