[SLING-5561] Resource Resolver Factory should be deactivated before provider is removed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.2.0, Resource Resolver 1.2.2, Resource Resolver 1.2.4, Resource Resolver 1.2.6, Resource Resolver 1.4.0, Resource Resolver 1.4.2, Resource Resolver 1.4.4
• Fix Version/s: Resource Resolver 1.4.8
• Component/s: ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 26/Feb/16 12:18
• Updated: 14/Mar/16 16:45
• Resolved: 02/Mar/16 15:54

Description

When a required resource provider is unregistered, this provider is first removed from the set of providers, and then the resource resolver factory is unregistered. During this process of unregistering, components might still try to use the resource resolver factory (which is valid) and according to the OSGi service model, the service should be still usable.
However, as the required provider has already been removed, the service is not usable anymore - which in turn might result in strange problems in services.

Issue Links

• relates to: SLING-5602 The Discovery module does not work any more after a ResourceResolverFactory reactivation