[SLING-4974] Observation support is using a stale resource resolver if resource resolver factory is restarted

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.5.0
• Fix Version/s: JCR Resource 2.5.6
• Component/s: JCR
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 28/Aug/15 09:01
• Updated: 14/Sep/15 15:59
• Resolved: 28/Aug/15 09:05

Description

If the resource resovler factory is restarted (e.g. through a configuration change of that factory), the observation support will not update the resource resolver as it is not properly tracking the resource resolver factory service

Issue Links

• is duplicated by: SLING-5023 ResourceResolver bound in ObservationListenerSupport is stale after the configuration for the Resource Resolver Factory (PID: org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl) is touched