Listener to detect when a session becomes dirty

ap_develop · **Joined:** Mon Oct 17, 2005 9:35 am **Posts:** 3

Hi!

Is there an easy way to detect when a session becomes dirty?
I need a listener or something that notifies me as soon as
the state of an object under hibernate's control has been changed.

My application has a "save-button" which is normally disabled. It
should become enabled automatically when the users changes
the value of an object. I tried to use an interceptor to solve this problem,
but "onFlushDirty" is called not until the transaction is committed, which is
too late.
TIA

Thomas

pksiv · **Posted:** Mon Oct 17, 2005 9:52 am

ap_develop wrote:

Hi!

Is there an easy way to detect when a session becomes dirty?
I need a listener or something that notifies me as soon as
the state of an object under hibernate's control has been changed.

My application has a "save-button" which is normally disabled. It
should become enabled automatically when the users changes
the value of an object. I tried to use an interceptor to solve this problem,
but "onFlushDirty" is called not until the transaction is committed, which is
too late.
TIA

Thomas

Do you really think it's good design to have your front-end functionality depend on your persistence mechanism ?

ap_develop · **Joined:** Mon Oct 17, 2005 9:35 am **Posts:** 3

pksiv wrote:

ap_develop wrote:

Hi!

Is there an easy way to detect when a session becomes dirty?
[...]

Do you really think it's good design to have your front-end functionality depend on your persistence mechanism ?

It doesn't matter what I think or don't think. It's a requirement
from the management I have to deal with.

Thomas

jamie_dainton · **Posted:** Mon Oct 17, 2005 10:33 am

Don't build it into the persistence mechanism.Build it into the business model. When a POJO/Business entity becomes dirty fire an event that your GUI can resond to.

Pksiv is correct, you managers can demand what they like and their demands can be met in a sane and sensible manner.

ap_develop · **Joined:** Mon Oct 17, 2005 9:35 am **Posts:** 3

jamie_dainton wrote:

Don't build it into the persistence mechanism.Build it into the business model. When a POJO/Business entity becomes dirty fire an event that your GUI can resond to.

Thank you, I will do that.
Our old persistence framework had such a handy feature.
I hoped there was a similar one in hibernate.

Thomas