Introduced lock functionality to ConcurrentModificationCheckConcern #11

Merged
merged 1 commit into from Mar 15, 2013

Conversation

Projects
None yet
2 participants
Member

arvidhuss commented Mar 11, 2013

We experienced simultaneous entity updates on the same entity from different clients hence different Uow's, because ConcurrentModificationCheck Concern had no read/write lock.
The ordinary lock concerns kick in far to late to prevent entity state version korruption.

@arvidhuss arvidhuss Introduced lock functionality to ConcurrentModificationCheckConcern t…
…o prevent simultaneous updates of the same entity.
4da4e22

@eskatos eskatos added a commit that referenced this pull request Mar 15, 2013

@eskatos eskatos Merge pull request #11 from arvidhuss/develop
Introduced lock functionality to ConcurrentModificationCheckConcern
Reviewed by Rickard and Niclas.
fbdec84

@eskatos eskatos merged commit fbdec84 into Qi4j:develop Mar 15, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment