Anybody know any patterns (better if implemented patterns) for working with StaleObjectStateException?

Look at this two questions, witch can explain need of this patterns:

1
If we need save set of entities in second session and one or more of this entity are stale, how we can more powerful check versions and demarcate conflicts?
Each entity - (vertex of complex graph of objects) or (simple objects)

2
How we can implement merge?
replicate() or setVersion() or another?

If any know more questions, plz post this questions.

Thnks All.

...

The above is from the session javadocs. So you should not at least try to commit the transaction.

Oh really?

This rule know all and i am too.

Are you read my question?

May be I really did not undestand your question. Can you be a little more clear?

I try again describe my question.

Little note from "Hibernate In Action":



I am interested second way (catch the exception).
But in this book (also in hibernate reference and forums) I not find any exapmles or implementations or at least any descriptions how I can do this.

I may use replication(obj, ReplicationMode.OVERWRITE) or setVersion() + merge()?
(also many other questions burn when i try implement this behavior)

Thnx.

I think the manually setting of the Version can be dangerous, because an another user can in this time edit the same data and thus increment the Version, in this case you will try to save the object with the smaller version as the object stored by another user.

Probably I or You do not understand the question correctly.
:)

Look at this code example, which written by me.


Customer dbObj = (Customer) session.get(Customer.class, myObj.getId());
myObj.setVersion(dbObj.getVersion());
session.merge(myObj);

where
dbObj - object version in DB, which has been saved while we thinking about changes on our object (во .а.ну. Ж))
myObj - our object with our changes

Realy we change only version of our object (not in DB), because we give version from DB and set this version for our object and than merge object.
Even if 3d (4d ...) user also change any property, our version can not be same, because we not edit(increment) version in DB (we tune our version to DB version ;)) and we will give StaleObjectExecption =-O.

So, how we can kill this recursion (ofcourse if first part of implementation completely good) ?

Rate/comment this idea plz.

Ok now it is clear:)

I took a look on the default Hibernate implementation of the Replicator, it seems that it makes at the OVERWRITE mode the same as you try to make

Oh, really?

This is good surprise for me :).

I want summarize our talk.

From two approaches (replicate() and myObj.setVersion()) wich is better?

Replicate don't check version, therefore if more than 2 concurrently working users will provide changes to same object replicate() should occur inconsistent data (if 3d user alrady made changes no Exeption throw when we replicate())

Also replicate() update all other object graph points without version checking.

So, I am choice my pure implementation of replicate() (setVersion()).
Is this right way?
:)

Thnx.