I think it would be helpful if you described in a little more detail how you want to use the MC in JBoss Cache. We can already use the MC to build a configuration and pass it to the existing CacheFactory methods to instantiate the cache. This is what AS trunk already does for the web session and EJB3 caches. So I don't think that kind of thing is what you're talking about. When you've mentioned this before I always had a vague notion in my head of using the MC to wire together the cache internals, i.e. build interceptor chains, plug in state transfer managers, etc. But what's never been clear at all to me is how this would work in terms of what the end user would configure. I wouldn't think we'd want 99% of end users having anything to do with anything beyond the existing Configuration object. I guess a goal is to allow the remaining 1% to override some stuff, e.g. add an extra interceptor. (Adrian, +1 on the thanks for the cache-specific schema suggestion; I've written a few -beans.xml files to create a cache now, and this would be a big improvement. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077042#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...