[infinispan-dev] New config - next steps

[Manik Surtani]

Since (1) is largely handled by a helper method on TestUtil or on the base test class, it should be fairly easy.  There will be a few exceptions, of course, but this approach should make it simpler than you'd expect if the new config API follows similarly named methods to the fluent API.

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:
> 
> 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. Anyone got a good suggestions about a good section for me to start in? (Not too in-depth domain knowledge needed, isolated, simpleish config)
> 
> 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

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org