To learn how to use optimistic locking, I tried to create a very simple example program.

I have a simple Person entity, with a primary key, two properties firstName and name, and a version field (of type int).

Creating a Person and saving it gives it a version of 0. Now, if I just do


the version field in my Person is incremented, even if the Person instance was not changed (not dirty). My expectation was that the version fields was only incremented when a "dirty" person was updated.

Is incrementing the version number on each update the expected behaviour, or did I miss something (maybe some configuration issue)?

You can check if an object is dirty before updating:



HTH, Maik

method session.update() will always execute sql update to database , no matter if object is dirty or no. it also attach object on session, if it was in detached state before.
So this method is good to persist changes on detached objects, because it always update object in db and also in ur case increment version.