anonymous wrote : | | One thing I noticed is the Configuration.getRuntimeConfig() object now exposes the NodeFactory as a property. | | I added this so that the NodeFactory is constructed and registered when the Cache is created, and gets a reference to CacheImpl when constructed such that methods that call createNode() need not worry about passing in details such as node type (as this is gleaned from the configuration attached to the cache) or bother passing in a cache reference. anonymous wrote : | This opens up the possibility of having a specialized factory create specialized nodes for _JBossInternal_. For example, one whose data version is always 0, or that has a more complex structure for holding child nodes to avoid lock conflicts, etc. | This possibility always was there, even the way the NodeFactory was used before - and still is in JBC 1.x.y - as a Singleton. That's the whole purpose of a factory. The first step would be to identify how a _JBossInternal_ node would differ from normal nodes, wrt. concurrency with optimistic and pessimistic locking, data versioning and BR as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998681#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...