Both of you are perfectly right. Since OSGI is not a requirement in my
project I'll see if I can invest some time in testing the new
functionality. I'll let you know about my results.
Cheers,
Christopher
Am 29.09.2011 09:32, schrieb Bengt Rodehav:
Yes that is correct.
I think the functionality is very useful and I did get it to work when
running outside of OSGi. However, in OSGi there seems to be a class loading
issue that prevents OpenJPA from finding my auditor class.
For me, OSGi is a requirement but for those who do not require OSGi, I think
trying/testing the audit log functionality would be much appreciated.
/Bengt
2011/9/28 Pinaki Poddar<ppod...@apache.org>
I'm looking forward to the next release then! :)
Following Linus' Law (""given enough eyeballs, all bugs are shallow"), if
more people test it out, then OpenJPA will have a "bug-free" release.
I was hoping that so much interest in Auditing (a mail chain with 60+
replies) will make some people to try out the new Audit facility. It is
designed with the view that the actual audit information and destination of
that information is controlled by the user application.
So far, Bengt had been trying it out and he did report that the customized,
user-written Auditor failed to plug-in in OSGi environment (which I have
not
yet fixed or able to fix). Otherwise, he found the API and functionality
usable.
-----
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Problems-getting-the-old-state-of-a-Map-auditing-tp6807638p6841782.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
