Hi,

Is there a way to get the original values of a property using Hibernate?

i.e. For all our entities we need to support an addiational getter "getOriginalValue()", as Hibernate uses an internal cache to maintain the state or to find out "isDirty()", is it possible to expose this functionality to the application?

Thanks,
Mel

You may look into using the Interceptor interface.

You attach it to your session:

and then whenever Hibernate flushes the session, onFlushDirty(...) gets called, with a list of 'original' property values. The list of original values will be empty (null) if you happen to flush a (previously) detached object, or a new object instance.

Granted, it is not exactly what you are asking for, but maybe it could help.

Another option is [possibly a way to implement session.isDirty(Object obj)]

using methods such as:

but I admit I have not done it - and there is probably more to consider.

Don't forget to rate this reply (if it did help).
Martin

I wrote:


This approach may be far more than where you want to go - starting with the fact that getPresistenceContext() is an implementation detail (SessionImpl), and the complexity goes up from there.
There are many possibilites (starting with a variety of states in which your object may be - from not initialized to deleted), and a lot of Hibernate internals...

Hi Martin,

The tip was useful, I already found the persistentContext.

For some reason the 'persistentContext' was not exposed via the session interface but via sessionImpl.

It works fine as long as the entity is attached to a session.

Thanks,
Mel

Please, do not forget to rate my post then... Thanx


Almost everything in Hibernate 'works' only within a session scope.
Detached objects only work when 're-attached' back - and then they are then considered totally dirty.

The original book warned against long sessions, but without them, why use Hibernate? The new book favors long sessions in 'one conversaction or one thread', but one has to be carefull.

We over-did it, and our very-long-sessions ended up in a hell of evictions (trying to avoid caching things forever).
So our latest invention are 'session objects' - object hierarchies carrying session along with them, closing session when we dispose of them. Also helps keeping our transactions separate (as Session transaction commits ALL session changes ... well, unless...).

Martin