openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bengt Rodehav (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (OPENJPA-2030) Build auditing facility
Date Tue, 26 Jul 2011 23:35:10 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071434#comment-13071434
] 

Bengt Rodehav edited comment on OPENJPA-2030 at 7/26/11 11:34 PM:
------------------------------------------------------------------

Attached AuditLogTest.zip which shows that only updated values are initialized when using
the SaveFieldManager in a @PreUpdate callback.

      was (Author: rodehav):
    Test case to show that only updated values are initialized when using the SaveFieldManager
in a @PreUpdate callback.
  
> 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

        

Mime
View raw message