[infinispan-dev] New config - next steps

[Mircea Markus]

On 23 Nov 2011, at 14:15, Pete Muir wrote:

> All,
> 
> Now that the new config API is in, and the basic teething pains resolved (thanks to Mircea and Kevin!), this is my plan to eradicate the old config:
> 
perhaps make the internals use the new config would be the first thing to do IMO - if new configs need to be added then people can ignore the old config entirely.
> 1) Convert test suite to use new config. This is a big job, so I'm going to ask for help on this! What I suggest is that I do a bit, and then we use this as an example/design.
I guess we'll have to assign packages/modules to each of us, otherwise it will happen that certain classes still use the old code. Which is not necessarily a bad thing.
>  
> Anyone got a good suggestions about a good section for me to start in? (Not too in-depth domain knowledge needed, isolated, simpleish config)
Hmm, a tricky bit will be the MultipleCacheManagersTest/SingleCacheManagersTest as these operate on the old config and not sure adding mirror methods (i.e. to operate on new config) would be the way to go as this would make the API hard to use. 
> 
> 2) Switch out parsers - with the test suite over this should reveal any problems in the parser
> 
> 3) Switch out the usage of the config objects, changing from converting new -> legacy to vs. versa…
> 
> Pete
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev