JBC does have a mechanism for encapsulating the classloading aspect (TreeCacheMarshaller) and an API for code that uses it to register the classloader and manage the lifecycle. We need to be sure to use this mechanism for our own services that use JBC (i.e. doing that in Hibernate is the fix for JBCLUSTER-150.) Problem with this is it requires an integration layer to register the classloader, manage the lifecycle, etc. It's also built around an assumption that different regions of the cache use different classloaders. Overly complex and painful for a simple ear that wants to deploy a cache from the ear and use it. It would be nice to make it easy for a user to specify during the configuration stage that the TCCL should be registered as the classloader for the entire cache and that the ordinary create/destroy lifecycle methods should deal with the classloader. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989444#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...