Rickard Öberg schrieb:
On 8/2/11 22:12 , Falko Bräutigam wrote:
I'm about to implement this. Seems to work well. Strong references for
timestamps and a (valid) cache for the states.
But now, after a ConcurrentEntityStateModificationException occurred and
the user has "merged" the entity versions, I don't see a way to tell the
ConcurrentModificationCheckConcern that this entity version is now
"merged" and hence "valid" (if it was not modified after this merge,
which I cannot detect either). Do I miss something?
What is a "merge"?
As there are now a modified version of an entity in the backend store and
modifications in the Uow of the user, the user has to decide what values are
"valid". Maybe the user is presented an UI with two editors side by side: my
version and the stored version. After this the entity is valid "by definition"
(as long as since last read from store timestamp has not changed again.)
-Falko
--
Falko Bräutigam
http://polymap.org
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
