[SLING-12019] Avoid duplicate ResourceResolverFactory registrations

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.10.0
• Fix Version/s: Resource Resolver 1.11.0
• Component/s: ResourceResolver
• Assignee: Julian Sedding
• Reporter: Carsten Ziegeler
• Created: 06/Sep/23 05:11
• Updated: 11/Oct/23 13:12
• Resolved: 18/Sep/23 12:40

Description

It seems that in some situations a new resource resolver factory is registered without unregistering the old one - which leads to two factories being registered. As not all components do eager service binding, these components stick to the old factory - and the old factory in turn is basically "empty" meaning all resource providers are unregistered. This prevents those components from reaching any resource, although everything looks fine.

Issue Links

• is related to: SLING-12090 sling-mock: Make compatible with ResourceResolver 1.11.0
• links to: GitHub Pull Request #100
• links to: GitHub Pull Request #104