For now, I'm not even sure I want this end-user configurable. I as a developer currently need it configurable so I can easily benchmark the effect of using JBoss Serialization. Based on those results we can then decide if we want it to be end-user configurable. But for my temporary purposes configuration via a system property is more than adequate. So, as we discussed, please do it that way. Go ahead and invent any property you want, just make sure it's prefixed with 'jboss.' If we later decide we want it to be end-user configurable I'd lean toward #1. The difficulty with #2 is a JBossCacheManager isn't a regularly deployed MBean service where you can dependency inject. The dependency injection would be to the Tomcat service, and TomcatDeployer would then have to programmatically pass it into the JBossCacheManager. I'd prefer not to do that, as 1) it makes Tomcat service more brittle by adding a dependency that's only needed for a specialized case and 2) it further couples the deployer and the manager. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967922#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...