[jbosscache-issues] [JBoss JIRA] Updated: (JBCACHE-1462) Capturing statistics and binding to JMX should be controlled by separate config options

[Manik Surtani (JIRA)]

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

Manik Surtani updated JBCACHE-1462:
-----------------------------------

    Fix Version/s: 3.2.0.GA
                       (was: 3.1.0.GA)


> Capturing statistics and binding to JMX should be controlled by separate config options
> ---------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1462
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1462
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: 3.0.1.GA
>            Reporter: Manik Surtani
>            Assignee: Manik Surtani
>            Priority: Minor
>             Fix For: 3.2.0.GA
>
>
> Comment from a contributor on JBCACHE-1444:
> "
> Users should be able to instruct jboss cache to add CacheMgmtInterceptor to interceptor chain without registering it as MBean, because they may want to register all beans themselves. There should be a separate flag to exclude the interceptor from the chain.
> Currently, the only workaround I found is as follows:
> Cache cache = factory.createCache(configFileName, true);
> CacheMgmtInterceptor cmi = new CacheMgmtInterceptor();
> cache.addInterceptor(cmi, 0);
> CacheSPI cachespi = (CacheSPI) cache;
> cachespi.getComponentRegistry().registerComponent(cmi, cmi.getClass());
> But I do not think users should be forced to do such hacks :) "

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira