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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Testing Sling Mock 3.5.0
• Fix Version/s: Testing Sling Mock 3.5.2
• Component/s: Testing
• Assignee: Henry Kuijpers
• Reporter: Henry Kuijpers
• Created: 12/Jun/24 08:25
• Updated: 6 days ago 13:45
• Resolved: 6 days ago 13:45

Description

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.

Issue Links

• links to: GitHub Pull Request #40