Again an interesting solution. Although, as I wrote previously, I intend to store the whole object and therefore don't need to keep track of what has changed. I intend to do a JSON diff when viewing the audit log in the GUI instead.
Your approach does, however, very elegantly solve the problem of how to store the audit log in the database with JPA since you actually store it in the object itself. /Bengt 2011/7/7 Mark Struberg <strub...@yahoo.de> > Hi Folks! > > I also use auditing with OpenJPA: > http://struberg.wordpress.com/2010/07/31/howto-changelog-with-jpa/ > > but it currently only works with a patched OpenJPA 2.2.x version. > https://issues.apache.org/jira/browse/OPENJPA-1873 > > We fixed a few parts already, but the POST_LOAD_ON_MERGE isn't yet > submitted since we didn't quite agree if it is spec conform. > > LieGrue, > strub > > > --- On Thu, 7/7/11, Pinaki Poddar <ppod...@apache.org> wrote: > > > From: Pinaki Poddar <ppod...@apache.org> > > Subject: Re: Audit log with OpenJPA > > To: users@openjpa.apache.org > > Date: Thursday, July 7, 2011, 7:58 PM > > Hi, > > Good to see lot of new ideas about auditing. > > Here is one more [1] that uses OpenJPA specific > > internals of accessing the > > original state of an entity. > > The comparison of the current state and original state to > > decide upon the > > audit message is provided trivially in this example -- but > > at the level at > > which OpenJPA API is being accessed here, much more > > facilities are available > > to compute the 'delta'. > > > > [1] > > > http://webspherepersistence.blogspot.com/2009/01/auditing-with-openjpa.html > > > > ----- > > Pinaki > > -- > > View this message in context: > http://openjpa.208410.n2.nabble.com/Audit-log-with-OpenJPA-tp6557932p6559730.html > > Sent from the OpenJPA Users mailing list archive at > > Nabble.com. > > >
