OK, I see your point. My expectation was StatefulTreeCache remains part of core, as does the factory class I mentioned in my first post. The factory uses org.jboss.cache.Version to detect the JBC release that's available. That adds a dependency on JBC to core, but only on the very stable API of the Version class. The factory instantiates the adapter delegate via reflection. The adapter delegate lives in a JBC-version-specific project. The dependency of core on org.jboss.cache.Version isn't so good. IIRC, StatefulTreeCache itself is instantiated via reflection, so it and the factory can certainly be moved out of core. But your statement about needing a basic roadmap is certainly valid; this all needs to fit into an overall architecture of what the core is, what the adapters are, etc. My main concern to this point has been being sure it *could* be abstracted without too much pain; I think that's the case. I don't intend to actually do the abstraction until we have an overall plan. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984194#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...