[
https://issues.apache.org/jira/browse/OPENJPA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088259#comment-13088259
]
Bengt Rodehav commented on OPENJPA-2030:
----------------------------------------
Just interested to find out whether you've come to a decision as to what to
support. I guess a first step is to provide the necessary plumbing to make it
possible for a developer to implement audit logging. Long term I think
something like Envers would be good for OpenJPA.
I would really like some basic support in the next version of OpenJPA since
it's a mandatory feature for "enterprisy" applications.
> Build auditing facility
> -----------------------
>
> Key: OPENJPA-2030
> URL: https://issues.apache.org/jira/browse/OPENJPA-2030
> Project: OpenJPA
> Issue Type: New Feature
> Components: kernel
> Reporter: Pinaki Poddar
> Attachments: AuditLogTest.zip
>
>
> Auditing or change tracking is an important function for transactional
> systems.
> We have sufficient support to build a facility that will allow the user to
> mark an entity @Auditable and an AuditManager to capture the changes in a
> transaction for @Audiatble instance via existing callbacks.
> Such an AuditManager should be configurable for the user to decide where the
> audit information being persisted (could be the same database, a separate
> database or something entirely different such as JMS queue or a file (or a
> printer, as someone had suggested).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
