Hi,
Could the Auditor (or an AuditorFactory) be set via some property on the
entityManagerFactory?
If it could it would remove any need for class loading from this part of
OpenJPA, because it puts the responsibility on the user to construct it
how they want.
It would also let them set it to a fully formed object, with access to
any other objects they have - the property setting supported within
persistence.xml is rather limited compared to what could be done with
Spring/Blueprint.
At the moment the only way I can see of passing information from the
outside world to OpenJPA is via the jpaProperties - which is limited to
strings.
It may be that to provide this feature we'd need some kind of
global/singleton/static OpenJPA world object to use for passing
non-string-stuff into OpenJPA.
Jim
On 28/06/2012 02:10, Pinaki Poddar wrote:
Kevin,
I may have done something non-kosher with openjpa.Auditor property. And I
did not test it in OSGi environment either. Bengt had reported earlier
classloading issues. It may be worthwhile to try this Auditor within an OSGi
environment, if one is set up to work with OpenJPA.
First thing we need to ascertain whether it is openjpa.Auditor is loaded
in a non-standard way than other custom plugins. But unfortunately I do not
have an OSGi environment to test.
-----
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context:
http://openjpa.208410.n2.nabble.com/OpenJPA-Audit-tp7580377p7580424.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
