Another thing I've thought about is renaming the TreeCache class to CacheImpl or something. We don't code to be written against the TreeCache class itself. There's a lot of legacy code written that way; changing the class name forces a shift to the new API. A kinder gentler way is to create CacheImpl, and then make TreeCache a trivial subclass. Then mark TreeCache deprecated with a comment it will be removed in 2.1 or 2.2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994706#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...