Ok On Mon, Oct 4, 2010 at 2:19 PM, Rickard Öberg <[email protected]> wrote: > On 2010-10-04 14.07, Niclas Hedhman wrote: >> >> Also, I am right now looking at >> >> EntityStore.visitEntityStates( EntityStateVisitor<ThrowableType> >> visitor, ModuleSPI module ) >> throws ThrowableType; >> >> and in the implementation JSONMapEntityStoreMixin, a DefaultESUOW is >> created, meaning the Usecase would be needed. >> >> Options; >> 1. Provide a Usecase which doesn't cache. >> 2. Grab the Usecase from UnitOfWork via >> ModuleInstance.unitOfWorkFactory().currentUnitOfWork(). >> 3. Add a Usecase argument. >> >> Not sure what is most suitable... > > I would prefer 1. I can't think of any good reason to cache while traversing > the entitystore. > > /Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev >
-- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
