On Mon, Jan 4, 2010 at 5:02 PM, Rickard Öberg <[email protected]> wrote:
> I would prefer to not do this, and instead do the "cleanup method" in the > TestData service interface that I mentioned. That should also have the > benefit of being much faster than an external traversal. For the memory > store it's basically a drop of the hashtable. There is even a comment left behind in the code (probably by you), saying "this works for reading, but not updating, removal..." If we decide to all traversals of UnitOfWork and a EntityType, then this will escalate quickly. Perhaps the solution is to solve it for API level. Cheers -- 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
