Hi people,


I have a doubt on concurrency control for a web application:

Suppose i am updating an object with id X. I just opened a new form and i'm editing the data. The problem is that i'm too slow, and Mr. M also wants to update the same data as i. As he is much faster, he did everything and saved it while i was still editing the data.

Finally i try to save, but Mr. M had saved before and the database should give me an error message. If i use simple <version> property, it won't work, because when i get the object properties after the submit, Mr. M will have saved his data.

We thought here of passing the old version value as a hidden object. We can make the version check in our application, but this is not desirable. Is there way to check this automatically? We tried setting the version to an older value to check if hibernate would complain, but it doesn`t. Actually, it simply ignore our attempt to set the version value and it increments it as expected.

Any ideas on how to solve our problem? Thanks a lot!

No ideas?

Hibernate would give an error for the case you mentioned if you are using optimistic locking i.e. <version> tag.




submit here refers to Mr M's submit?

If you are again reading the data, after Mr M has saved then obviously there would be no error since you are working on the latest data.

Not sure if I understood what your problem is..

Even we are facing the same issue. If any one has the solution , please let us know ---

Seshadri , Bangalore