[
https://issues.apache.org/jira/browse/OPENJPA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071432#comment-13071432
]
Bengt Rodehav commented on OPENJPA-2030:
----------------------------------------
It seems like it is not possible to retrieve the values of the previous version
of an entity. Only the values that have actually been updated can be retrieved
- the rest are uninitialized. I attach a test case to prove my point.
I've used the SaveFieldManager in a @PreUpdate callback in an attempt to store
a serialized version of the previous version of the entity whenever the entity
is updated. I do not only want to store the changed values but the whole entity.
This functionality must be available and also possible to achieve in a
supported audit log.
> 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
