Hello there Jim, I was part of initiating that support for OpenJPA (Pinaki implemented it) but I haven't used it myself yet. The reason is that I couldn't get the class loading to work when running within OSGi. There is still an outstanding issue regarding this:
https://issues.apache.org/jira/browse/OPENJPA-2052 What is your runtime platform? Also, does anyone know whether any progress is made regarding class loading within OSGI? Many people prefer OpenJPA over Eclipse and Hibernate because it works better in OSGi than those projects. However, the OSGi support in OpenJPA is unfortunately very fragile and really needs to be improved. For me, the lack of OSGi support is very frustrating. OSGi is a requirement for me and I really would like to use the new auditing functionality. /Bengt /Bengt 2012/6/22 Jim Talbut <jtal...@spudsoft.co.uk> > Just want to say thanks. > > Some time ago I was involved in a discussion here about doing audit using > lifecycle listeners. > There are a whole bunch of problems with this approach and, although my > implementation worked, it was not specified that it would work. > > Yesterday I needed to add an audit facility to a system and noticed the > new @Auditable annotation (http://openjpa.apache.org/** > builds/2.2.0/apache-openjpa/**docs/ref_guide_audit.html<http://openjpa.apache.org/builds/2.2.0/apache-openjpa/docs/ref_guide_audit.html> > ). > Wow. > I spent some time worrying about how to write the data to the database - > assuming I'd have to use JDBC and worrying about how to inject the data > source. > Then I noticed that the Broker passed lets me persist a new Entity during > the audit. > > Thank you guys. > > Jim >
