Re: QueryCache injection problem with multiple runtimes

2016-06-30 Thread Andrus Adamchik
> On Jun 30, 2016, at 9:23 PM, Andrus Adamchik wrote: > > > Module m1 = (binder) -> binder.bind(QueryCache.class).toInstance(new > EhCacheQueryCache("name1")); > Module m2 = (binder) -> binder.bind(QueryCache.class).toInstance(new > EhCacheQueryCache("name2")); Or rather new EhCacheQuery

Re: QueryCache injection problem with multiple runtimes

2016-06-30 Thread Andrus Adamchik
Hi John, > runtime.getDataDomain().setQueryCache(queryCache); > But this actually does *nothing*. The DataContextFactory uses the > QueryCache that was set by the injector and ignores this later > modification. This method should be removed or even better - made to work. This method actually wo

QueryCache injection problem with multiple runtimes

2016-06-23 Thread John Huss
I'm starting to use QueryCache for the first time, and I'm using EhCache since OSCache is a dead product. My app creates two separate runtimes that are identical, but separate. If I configure both to use EhCache with the module: public class AppModule { public void configure(Binder binder) { bin