So looks like we should just provide @Replicable (or @Replicated) and give the semantics of it applies to all subclass as well. Later on when AOP can provide attribute matching, we can then add the attribute (subclass=true) to distinguish it. One other possible way to break the closure is actually to comment out the prepare...instanceof... statement in pojocache-aop.xml. But it applies to all POJOs so not a permanent solution. Ideally, I'd like to get this done before Brian start the integration into 5.0. This is becuase there are tedious changes for the testing POJOs there (unless he doesn't object). OK, it is between @Replicated and @Replicable. Elias has convinced me to switch over to @Replicable (like I mentioned). So looks like it is 2 agaisnt 2. Anyone else wants to cast the switching vote? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986376#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...