openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2030) Build auditing facility
Date Thu, 14 Jul 2011 21:06:59 GMT

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

Kevin Sutter commented on OPENJPA-2030:
---------------------------------------

from Bengt Rodehav bengt@rodehav.com via openjpa.apache.org to dev
	
Excellent idea!

I think it's probably good to have the actual logging (serialization or what
not) pluggable since that's an area where people will have very different
requirements.

/Bengt

> 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
>
> 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