I think that would be OK for usage in the AS, but... does JBC have the ability to bind a Cache instance in JNDI? AFAIK when we do that now we're relying on the AS's proxy factories. For the standard caches in the AS we could always add beans to the config files to do this, but that doesn't work outside the AS. The usage I have for accessing the cache via JMX is in AS unit tests, for which JNDI would be fine. The other one I can think of would be more app-specific mgmt consoles, e.g. show me the names all the sessions in the cache for webapp X, which would use a JMX call to getChildrenNames. For a mgmt console people don't want to use JNDI as it leads to the need to have JBC classes available to the console. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971133#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...