Hi,

I have an application where a Java Swing Client can do several updates on an object graph of entities. All entities have an optimistic locking version number. So, when i do an update on the server, I want to return to the client new version of each updatet entity. I thought that simply flushing the transaction and re-reading the object would do the thing. But i only get back the old version.

My code looks like this:

public Institution updateInstitution(final Institution pInstitut) {
Institution iold = dao.findById(pInstitut.getId(), true);


dao.getEntityManager().merge(pInstitut);
dao.getEntityManager().flush();

Institution inew = dao.findById(pInstitut.getId(), false);
inew.getContact();
return inew;
}

In the case where I do my tests I just change an attribute of the Contact entity. And this is exactly where Hibernate creates an Update statement. The problem here is: I don't get the new version of the updated Contact object.

Any suggestions please?

Carlo

I have a issue something like that. I am new to hibernate and I was invovled in upgrading to a newer version of hibernate ie3.2.5. Since the upgrade whenever any fiels is updated the a older version of the field is diplayed. This was not an issue with the prior version of hibernate.

Any thoughts

If I understand your problem correctly, you change an attribute of the Contact entity which means, you do not change the Institution entity at all.

So, why should it create a new Version of the Institution entity in question?

Regards,
Frank

I just wanted to make life easier -:). Institution is the root object of these business entities; it has a Contact, and a Contact has Addresses. As the client always needs these objects together, the associations are marked for cascading.
So, the nice feature is, I can just say 'UpdateInstitution' and Hibernate does the rest. In my example it detects that just Contact needs this update.

Then, by returning an Institution object, I really return the whole updated object graph (for further changes).

So, my problem is of course: for each object which was updated, I need the new object version.

BTW: my entities have this attribute:
@Version @Column(name = "OBJ_VERSION")
private int version = 0;

Carlo

Shame on me! I was TOO consternated by the problems reported - and as I saw now: produced - by the client that I didn't see that on the server side everything worked just fine. Hibernate and Entity Manager work as expected.

Sorry for this false alarm / noise!

Carlo