Rickard Öberg schrieb:
Hi,
In looking at potential simplifications of the UoW, I'm wondering
whether it would be ok to limit the number of involved EntityStores to 1?
In DDD there is already the suggestion to limit nr of changed aggregates
in a request to 1. I violate that sometimes, but in any case there will
NEVER be entities from several EntityStores involved in the same UoW.
So, does anyone have a case with several EntityStores being involved in
one UoW? If no, can we enforce that only one can be involved.
The reason is that the current commit handling is a bit complicated due
to having to allow several EntityStores to be used. Not a single
EntityStore supports this properly though, AFAIK. I would therefore
prefer to make it a "1 phase commit", which would probably also make it
easier to support the EventStore commit.
Would be bad for me I think. I have non-Qi4j stores in my app and I need to
synchronize commits over all data stores. I was rather about to ask if Qi4J can
expose the 2 phase commit in two separate calls so that UoWs can be controlled
be a transaction manager. With 1 phase commit this wouldn't be possible at all.
-Falko
--
Falko Bräutigam
http://polymap.org
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
