[infinispan-issues] [JBoss JIRA] (ISPN-5572) Exposed JMX MBeans should be separate components

[Tristan Tarrant (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-5572:
----------------------------------
    Fix Version/s: 9.0.0.Alpha3
                       (was: 9.0.0.Alpha2)


> Exposed JMX MBeans should be separate components
> ------------------------------------------------
>
>                 Key: ISPN-5572
>                 URL: https://issues.jboss.org/browse/ISPN-5572
>             Project: Infinispan
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 8.0.0.Alpha2, 7.2.3.Final
>            Reporter: Dan Berindei
>             Fix For: 9.0.0.Alpha3
>
>
> We currently expose internal components as JMX MBeans, and that makes our JMX "API" very unstructured. The exposed MBeans should be separate components, and the only concern in their interfaces should be ease of use.
> One example of JMX getting in the way of refactoring is {{CacheMgmtInterceptor}}. The interceptor chain is dynamic, so it should be possible to insert the interceptor only when statistics are enabled. But because the {{statisticsEnabled}} attribute is on the interceptor itself, that becomes a lot trickier, and we had to introduce a separate configuration attribute that disables statistics permanently (ISPN-5542).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)