Comments on: Automatically Populating Audit Columns in Hibernate

By: nix

nix — Wed, 06 Aug 2008 10:18:00 +0000

This seems like a really great advantage. Can you please post a simple demo application demonstrating the above example? Doing this would greatly help a novice like me. Thank you very much in advance.

By: Basil Vandegriend

Basil Vandegriend — Sat, 19 Apr 2008 20:41:10 +0000

I’m going to assume that you have a EJB Session Bean representing some service that a client application on a user’s desktop is communicating with.

At the initiation of processing within the session bean, you can store the user’s identity within the ThreadLocal and then the AuditInterceptor will do its magic.

The hard question is how do you obtain the user’s identity within the EJB Session Bean? This question applies equally, however, to the scenario where you manually set the audit columns instead of using AuditInterceptor – you still need to have the user’s identity. You can either manage security manually and pass in the user’s identity to the session bean method, or use the security provided by the application server.

By: Martin

Martin — Fri, 18 Apr 2008 15:36:39 +0000

Great tip. What would you suggest when you are updating some entity that was handed to you remotely through the remote interface of an EJB?

I’d love to use this style of interceptor, but I can’t use a ThreadLocal when the user is in a JVM on a desktop client somewhere far away.