[jboss-dev-forums] [Design of JBossCache] - Re: API Issues integrating 2.0.0.DR1 in HEAD

[bstansberry@jboss.com]

I've started working on #2 above. This work ties into what I think should be done for MC usage of the cache.

1) We already have configuration via DOM Elements and Properties of complex types like CacheLoaderManager.  We need to add the ability to configure via MC construction of POJOs that represent all the configuration elements.  The MC doesn't need to use Element/Properties to build up these POJOs.
2) Configuration becomes a composite object, with a contained CacheLoaderConfig, (new) BuddyReplicationConfig and (revised) EvictionConfig.
3) When the old Element/Properties style of configuration is used, all parsing of DOM elements/reading of Properties to populate the config objects should be done within the config objects themselves. E.g. pass an Element to the constructor of CacheLoaderConfig and let it parse it.  CacheLoaderManager constructor gets passed the CacheLoaderConfig, not an Element.  BuddyManager gets passed a BuddyReplicationConfig, not an Element.
4) The various config objects like CacheLoaderConfig are now exposed to user code via a getter in Configuration.  This means their setter methods are also exposed, so if those methods are invoked after the cache is started we need to check if that's allowed.  This is already done in Configuration; need to apply the same technique in the other config objects.

I've got a good start on this.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978370#3978370

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978370