I have a model object Person that I persist with hibernate.
I have a field versionNumber that has a @Version tag on it and I have a setter and getter (setVersionNumber and getVersionNumber). Optimistic concurrency control works fine and I can see that my version is incrementing properly and that concurrent changes are caught correctly.


I was expecting the following to fail:
int id = 1;
Person p = personDao.load(id);
p.setVersionNumber(p.getVersionNumber() - 1); // fake a change to an old version
p.setName("new name");
personDao.update(p); <--- I would expect this call to fail because I'm using an old version.

Is this related to the fact that my object is attached ?

Any thoughts?

I reckon it works because there's only process updating a record.

Try this


Person one update will change the version no. Thus, person two update will fail as its version no differs from the one in the database.

I think version should be read only property.

Hope it helps