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

anonymous wrote : | 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. | +1. anonymous wrote : | 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. | +1 again. Yes, this does give us a lot of flexibility in how we configure complex structures like cache loaders, eviction policies, etc. anonymous wrote : | I've got a good start on this. | Cool! This feedback really does help; I'm looking at cutting an Alpha once these changes are in. Since you already have a start on the config side of things, could I leave this to you? I'm hoping to tag the alpha later this week, perhaps on Thu. Does this work for you? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978804#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...