Attn: Gavin and Team - My name is Raj. My client is looking for consulting support on one of the Hibernate issue we are having. Do you guys provide such support ?
If yes you can reach me at 678 665 2219, else please recommend someone.

See my signature. ;-)

mmerder
Thanks for you reply.

We have the domain objects retrieved and brought to the front end, from the domain objects we make the Value objects. By the way our domain objects have audit fields like modified date, modified user. While making the Value objects from the domain objects we mistakenly did not copy the audit fields into VO.
When we copy the VO changes to DO to persist, since we did not copy the audit fields in the beginning, we could not copy the audit fields back to DO. Now you know what happens, even if there are no changes in the VO data, since the audit fields are null, hibernate is thinking this object is dirty and doing the unnecessary updates.

I thought i will copy previous state info into current state. No luck.

We tried all possible ways in Audit Interceptor findDirty method. This method either has same values in currentSate and previousState or no previousState at all. We debugged it many times.

So finally we are reaching out to get some help on tweaking the Hibernate source code itself to avoid dirty checking on audit fileds. Unless I hear some strange idea for now I think we don’t have any option than changing the hibernate source code itself.


Hope there is some strange idea which works -:). Let me know if you want to do this, we are ready to sign the SOW with you.

Not sure how reliable this is. We tried to ignore our audit fields in, need to test the application.............


DefaultFlushEntityEventListener dirtyCheck(FlushEntityEvent event) throws HibernateException


else {
// dirty check against the database snapshot, if possible/necessary
final Object[] databaseSnapshot = getDatabaseSnapshot(session, persister, id);
if ( databaseSnapshot != null ) {
dirtyProperties = persister.findModified(databaseSnapshot, values, entity, session);
IF AUDIT FIELDS MAKE dirtyProperties = NULL
cannotDirtyCheck = false;
event.setDatabaseSnapshot(databaseSnapshot);
}
}
}
else {
// the Interceptor handled the dirty checking
cannotDirtyCheck = false;
interceptorHandledDirtyCheck = true;
}

event.setDirtyProperties(dirtyProperties);
event.setDirtyCheckHandledByInterceptor(interceptorHandledDirtyCheck);
event.setDirtyCheckPossible(!cannotDirtyCheck);

Hi my answere is correct or wrong i don't know.
try this
include in mapping file for both the property

Hello,
sure we do, actually we employ a team of specialized consultants on Hibernate.
We're all employees of JBoss by Red Hat inc., so this is where you can get professional support from us directly:
http://www.jboss.com/
I'm personally in R&D, so can't phone you back myself; please get in touch with sales.

btw: I am one of the specialized consultants in europe. ;-)


Sounds good, have you tried that?