The Configuration class has a "serviceName" property that I can't find a good use for. I'd like to get rid of it as it leaks JMX concerns into the core code. CacheMgmtInterceptor was using it to figure out a value to add a data to a Notification. With JBCACHE-855 that's no longer the case. JmxUtil has some static methods that try to use the value to figure out an ObjectName. I don't think that's valid; any code (e.g. xxxJmxWrapper) that's doing a registration should know it's own ObjectName from MBeanRegistration. So, I'll clean that up. Any objections? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044768#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...