Hey, As outlined in previous emails about UoW, if a UoW complete()s and Entities used in it had changed, then a ConcurrentEntityModificationException should be thrown, and the client must either abort or refresh() the entities that had been changed. None of the EntityStores implemented the check though, so this part of the API wasn't exactly working.
I therefore implemented concurrent Entity modification checks in the JDBM store. Then I refactored it out to a Concern of its own, and moved it to the MemoryEntityStore package, so that all EntityStores now can trivially apply it as a Concern. Tada, the power of Composite Oriented Programming at work! I have added it to JDBM and Memory for now. There are some performance optimizations that could be done to it, but at least it works now. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
