2009/4/16 Rickard Öberg <[email protected]>: > If the stores recognize JTA, then they can perform the changes in 4.1-2,
> What say ye? I say that you have probably forgotten why it was the way it was... It was not about JTA transactions at all, AFAIR. It was to support that the UoW could use multiple ES, and if any one fails, no change would happen to any other. I am not sure that "Not many stores support it today" is an accurate statement. AFAICT, JDBM does, and your REST does not. I think Neo does, and my Swift is supposed to do it. Going from supporting our structure to JTA is a *huge* step, and not sure I like it at all. When we start getting the hang of Aggregates, the conclusion might be that Aggregates are not allowed to be spread across EntityStores, but I am still worried over a simple case; * Take an Entity from ES1. * Store the Entity in ES2. And be certain that it exists in one and only one ES, becomes a major client undertaking. I am not convinced that your suggestion is the right one. 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
