Re: [infinispan-dev] Cache Loaders configuration dilemma

I'd suggest to keep an interface in the API signature, much better than an abstract class. +1 to change the API, more changes are expected soon anyway. Sanne On 8 August 2012 18:51, Tristan Tarrant <ttarrant(a)redhat.com&gt; wrote: > Hi guys, > > as part of ISPN-1978, I'm migrating the Cache Loaders to the new > configuration builder APIs. I want to change the init() method of the > CacheLoaders which has the following signature > > public void init(CacheLoaderConfig config, Cache<?, ?> cache, > StreamingMarshaller m) throws CacheLoaderException > > to the following: > > public void init(AbstractLoaderConfiguration config, Cache<?, ?> cache, > StreamingMarshaller m) throws CacheLoaderException > > This will break all existing cache loaders/stores: I'll fix all the ones > bundled in the distribution, but do we need to provide compatibility > with third party loaders ? > > Tristan > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev