You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2013/03/28 16:27:16 UTC

[jira] [Resolved] (OPENJPA-2030) Build auditing facility

     [ https://issues.apache.org/jira/browse/OPENJPA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pinaki Poddar resolved OPENJPA-2030.
------------------------------------

    Resolution: Fixed
      Assignee: Pinaki Poddar
    
> 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
>            Assignee: 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira