[ 
https://issues.apache.org/jira/browse/OAK-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525741#comment-15525741
 ] 

Stefan Egli commented on OAK-4855:
----------------------------------

[~chetanm], could you pls have a look at OAK-4855 and JCR-4032? I think it 
would be a simple but useful, small extension. Thx!

> Expose actual listener.toString in consolidated listener mbean
> --------------------------------------------------------------
>
>                 Key: OAK-4855
>                 URL: https://issues.apache.org/jira/browse/OAK-4855
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>    Affects Versions: 1.5.10
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.5.11
>
>         Attachments: OAK-4855.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to