You'd have to write your own class to handle the JMX registration. You can see what CacheJmxWrapper does; you basically need a CacheSPI (to get the interceptors), an MBeanServer, and some algorithm for creating the ObjectNames for the interceptors.
Is your concern that the CacheJmxWrapperMBean interface has too much? If you post an MBean interface you want, I can look into creating a limited super-interface that you could expose. No promises though. Let me know how the Spring configuration goes. The JBC docs discuss using JBoss Microcontainer to build up a Configuration object, but I see no reason Spring wouldn't work just fine. I just haven't had time to do it to include in a doc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063209#4063209 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063209 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
