I am not sure whether it is a setting issue, my understanding or simply hibernate non-support.

Here is the problem:

I have a persistent object Applicant. I open a new session and retrieve an applicant that I already have in the databse. I transfer the object to a presentation layer, while the session that retrieved it goes away.

After a little manipulation of the object in the presentation tier it comes back and I try to save it. I open a new Session - s, and do s.saveOrUpdate (applicant). If my Applicant object is not changed and I do flush () an update is issued, which tells me that hibernate is not keeping the instance state with the instance but rather does it in the session. Is it correct?

Is there any way to keep the state with the instance, so that unnecessary updates are not issued? Maybe there is another way to achieve the same thing?

Does anyone has a clue?

Thanks,
Alex.

You're correct


session.disconnect(), session.reconnect()

there was a thread on that topic (state in object vs in session) some time ago, if I remember well.