Again an interesting approach. It's very similar to the way we did it in the old days (before O/R mappers were abundant). We rolled our own O/R mapping and also compared the previous state with the new state and saved the difference (XML in the database). I guess the same approach can be taken if OpenJPA internals are utilized.
This time I was not going to bother determining the difference but store the whole object in a serialized form. Thus, my problem is just how to being able to store the serialized form in the database. Thanks, /Bengt 2011/7/7 Pinaki Poddar <ppod...@apache.org> > 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. >
