Description
With SLING-6056 more listeners (in the form of ResourceChangeListeners) will be mapped 1:1 to either BackgroundObservers or JCR EventListeners. That means, they will also be exposed in the consolidated listeners stats. Without any change though, all that can be seen in that stats is the name of that 'bridge/mapper' listener (ie either JcrResourceListener or OakResourceListener), since currently all that is exposed is getClass().toString() - and the actual ResourceChangeListener sitting 2 steps behind is not visible.
In JCR-4032 I'm suggesting to introduce a getToString() to the EventListenerMBean, and once that would be available, this could be exposed in the ConsolidatedListenerMBeanImpl.
Attachments
Attachments
Issue Links
- blocks
-
SLING-6056 achieve 1:1 mapping between observation and resource change listener
-
- Closed
-
- is blocked by
-
JCR-4032 Add jmx EventListenerMBean.getToString() for clearer consolidated listener stats
-
- Closed
-