Why are 4 and 5 even good ideas, let alone "requirements"? As a user, I would want to specify where the static variable is stored and how and if it is replicated. The "registerClass" would essentially link a class to the cache. A class would have to belong to a single cache. To be fair, I'm not really involved with this feature at all. I'm not the customer. But here are what I believe are "requirements": 1. User needs to be able to specify which PojoCache they are replicating their object with. This is becaues it's a common use case to have multiple PojoCache instances per JVM. 2. User needs to be able to control (turn on/off) replication of the static fields. It needs to be off by default. This is because they might want to use this object in a situation where they aren't using JBossCache, e.g. on a simple client without JBoss Cache. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985110#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...