[jira] [Commented] (ISIS-3110) Defer audit trail publishing until end of transaction

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on ISIS-3110:
-------------------------------------------------------

Commit f427fbea15a081018034cbfbc6a54e4d2e94e783 in isis's branch refs/heads/ISIS-3110 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=f427fbea15 ]

ISIS-3110: introduces EntityChangeTrackerJpa, mirroring JDO impl, but leveraging the PropertyChangeRecords already provided to us


> Defer audit trail publishing until end of transaction
> -----------------------------------------------------
>
>                 Key: ISIS-3110
>                 URL: https://issues.apache.org/jira/browse/ISIS-3110
>             Project: Isis
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-M7
>            Reporter: Daniel Keir Haywood
>            Assignee: Daniel Keir Haywood
>            Priority: Minor
>             Fix For: 2.0.0-M8
>
>
> The current "light-weight" implementation (introduced in ISIS-2826) would seem to be a little too eager : when combined with the commandlog implementation - that flushes later on - i believe we are corrupting the internal UoW caches within EntityManager... it thinks that the id of AuditEntry's already persisted are being updated.
> The situation and error found is similar to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=333977.]
> So instead, defer the actual publishing until the end, the same way that JDO works.  But still leverage the property change records that JPA provides. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)