Hi,

I am trying to use hibernate optimistic locking on one of my entities. I have a field with JPA annotations as such:

@Version
@Column (name = "version_number")
private Integer version;


I have wiped the database to start afresh but something odd happens. I have created 3 new entities. When I modify the first hibernate runs update statements against the first And the second entity, hence version numbers increase for both. I cannot think of any reason why hibernate should try and update the second entity.

When I modify the second created entity, it works fine and only the version number for this one is incremented.

Modifying the third entity runs updates (and increments versions) for inself and the second entity, which is also unexpected (and unwanted).

Would appreciate if anybody has experienced anything similar and can offer any exoplantion.

(I am using JPA with hibernate underneath)

You might get more help if you post a code example

Well there isn't any interesting code really. I should have called the Subject: Problem with Hibernate Automatic Versioning. Hibernate increases the version number of the entity I modify and some others (not all). My service layer method that does the save is as follows:

@Transactional
public Long saveApplication(Application application) {

//Determine whether a new application or an existing application
Long applicationId = application.getId();
if (applicationId == null) {
//Persist new application
application.setStatus(Constants.APPLICATION_STATUS_INCOMPLETE);
populateApplicationFields(application);
entityManager.persist(application);
applicationId = application.getId();
} else {
//Update existing application
entityManager.merge(application);
}

return applicationId;
}

Before this is called, all applications are loaded using method:

@Transactional (readOnly = true)
public List<Application> loadApplications() {
Query query = entityManager.createQuery("from org.ec.tentec.domain.Application as application where application.status != 'CLOSED' and application.status != 'DELETED' order by application.projectCode");
List<Application> resultsList = query.getResultList();

return resultsList;
}

Then one is loaded by id for modification using method:

@Transactional (readOnly = true)
public Application loadApplicationById(Long applicationId) {

Application application = entityManager.find(Application.class, applicationId);
return application;
}

Any ideas appreciated.

I think I have solved this now. It looks like my dubious implementations of equals method thoughtout my domain classes (inclusion of primary keys used by hibernate) was causing odd automatic versioning behaviour!