You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/09/27 10:38:20 UTC

[jira] [Updated] (OAK-4855) Expose actual listener.toString in consolidated listener mbean

     [ https://issues.apache.org/jira/browse/OAK-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli updated OAK-4855:
-----------------------------
    Attachment: OAK-4855.patch

Attaching patch [^OAK-4855.patch]

> 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)