[SLING-6056] achieve 1:1 mapping between observation and resource change listener

• Type: Task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.8.0, API 2.14.2, Resource Resolver 1.4.18
• Fix Version/s: JCR Resource 2.8.2, API 2.15.0, Resource Resolver 1.5.0
• Component/s: API, JCR, ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Stefan Egli
• Created: 16/Sep/16 10:16
• Updated: 26/Sep/19 12:41
• Resolved: 19/Oct/16 09:39

Description

At the moment it seems there is a 1:n mapping between 1 OakResourceListener (and 1 BasicObservationReporter) and n ResourceChangeListeners. The idea however is to get rid of such a bottleneck and have a 1:1 mapping (that might or might not be in the BasicObservationReporter, that I don't know). We should implement such a 1:1 mapping.

See thread on dev list

Issue Links

• blocks: SLING-5994 Move from EventHandler to new ResourceChangeListener API
• is blocked by: JCR-4032 Add jmx EventListenerMBean.getToString() for clearer consolidated listener stats
• is blocked by: OAK-4855 Expose actual listener.toString in consolidated listener mbean
• is related to: OAK-4581 Persistent local journal for more reliable event generation
• is related to: SLING-6070 Reduce temporary storage required in JcrResourceListener, call reportChanges earlier