Audit Info Custom Type

jwboring · **Posted:** Fri Sep 12, 2003 8:04 am

I am questioning the validity of this design pattern in the community area (http://www.hibernate.org/48.html). I thought you couldn't
modify the entity in Interceptor. I've tried the following (even though the docs say don't) and I know that the changes made don't make it to db.

Code:

if( entity instanceof Auditable ) {
      MyEntity vo = (MyEntity) entity
      try {
          Timestamp timestamp = new Timestamp(System.currentTimeMillis());
          vo.setLastUpdated(timestamp);
      } 
      catch( Exception e ) { e.printStackTrace();}
  }
  return false;

Does the design pattern "magic" (AuditInfoType, final class AuditInfo, etc..) provide a way around this limitation? If so then why?

jeff.boring@siemens.com

max · **Posted:** Fri Sep 12, 2003 8:42 am

jwboring wrote:

I am questioning the validity of this design pattern in the community area (http://www.hibernate.org/48.html). I thought you couldn't
modify the entity in Interceptor. I've tried the following (even though the docs say don't) and I know that the changes made don't make it to db.

Code:

if( entity instanceof Auditable ) {
      MyEntity vo = (MyEntity) entity
      try {
          Timestamp timestamp = new Timestamp(System.currentTimeMillis());
          vo.setLastUpdated(timestamp);
      } 
      catch( Exception e ) { e.printStackTrace();}
  }
  return false;

Does the design pattern "magic" (AuditInfoType, final class AuditInfo, etc..) provide a way around this limitation? If so then why?

jeff.boring@siemens.com

The pattern works because AuditInfo is it's own type - you can change AuditInfo directly, NOT basic properties as you do in your example.

If want to change those properties you need to do it in the values array sent as a parameter to your interceptor.

efender · **Posted:** Fri Sep 12, 2003 8:45 am

Here's my Interceptor's onFlushDirty method:

Code:

if (entity instanceof Auditable) {
    AuditInfo ai = ((Auditable) entity).getAuditInfo();
    Timestamp timestamp = new Timestamp(System.currentTimeMillis());
    ai.setLastUpdated(timestamp);
    ai.setUpdatedBy(user);
}
return false;

However, I haven't tried an update yet. We are doing the cast and the assignment differently. I'll try an update and let you know if it makes it to the DB.

jwboring · **Posted:** Fri Sep 12, 2003 9:46 am

Thanks Max. I know about the values array but this pattern eliminates the looping - we've got some really big tables (lots of cols). Of course, this pattern might take longer than the looping :-)

Hey, what's the final business about? Is this mandatory?

Jeff

max · **Posted:** Fri Sep 12, 2003 10:00 am

jwboring wrote:

Thanks Max. I know about the values array but this pattern eliminates the looping - we've got some really big tables (lots of cols). Of course, this pattern might take longer than the looping :-)

If the audit fiels is in a AuditType then you won't have any problems !?
You are not following the design pattern - you are having the fields directly on the entity!

Quote:

Hey, what's the final business about? Is this mandatory?

Jeff

The final what ?

jwboring · **Posted:** Fri Sep 12, 2003 10:09 am

No Max, I will follow the pattern and use the custom type. My code was only listed as an example of what I thought you couldn't do. Your excellent & timely reply helped me understand this. Thanks,

Quote:

The final what ?

Code:

public final class AuditInfo implements Serializable {
       private Timestamp lastUpdated ;
       private Timestamp created ;
       private Long updatedBy ;
       private Long createdBy ;
   
       public Timestamp getLastUpdated()                 { return lastUpdated;  }
       public void setLastUpdated(Timestamp lastUpdated) { this.lastUpdated = lastUpdated; }
       public Timestamp getCreated()                     { return created; }
       public void setCreated(Timestamp created)         { this.created = created; }
       public Long getUpdatedBy()                        { return updatedBy; }
       public void setUpdatedBy(Long updatedBy)          { this.updatedBy = updatedBy; }
       public Long getCreatedBy()                        { return createdBy; }
       public void setCreatedBy(Long createdBy)          { this.createdBy = createdBy; }
}

max · **Posted:** Fri Sep 12, 2003 10:26 am

I would think it is a pretty good thing that your auditinfo class cannot be messed with by subclasses - you don't ?

jwboring · **Posted:** Fri Sep 12, 2003 10:36 am

OK, point taken. Thanks again! This real time support is really great. Why don't you just give me your phone number :-)

Jeff

max · **Posted:** Fri Sep 12, 2003 10:56 am

jwboring wrote:

OK, point taken. Thanks again! This real time support is really great. Why don't you just give me your phone number :-)

Jeff

Because that you cannot afford ;)

BuddhaBuddy · **Joined:** Tue Oct 09, 2007 11:53 pm **Posts:** 5

Is this still the accepted method to create an Audit, or has a more standard method come along in the last few years that works better?

There are many more methods in UserType and Interceptor now, some of which look very useful, and the signature for Hibernate.TIMESTAMP.deepCopy() has changed.