[jira] [Resolved] (ISIS-1041) Under certain circumstances, appears that auditing can cause the same tuple to be audited within a single transaction.

["Dan Haywood (JIRA)" <ji...@apache.org>]

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

Dan Haywood resolved ISIS-1041.
-------------------------------
    Resolution: Fixed

> Under certain circumstances, appears that auditing can cause the same tuple to be audited within a single transaction.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-1041
>                 URL: https://issues.apache.org/jira/browse/ISIS-1041
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: core-1.7.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: core-1.8.0
>
>
> In the case of the Isis addon's implementation of auditing, there is a unique key constraint on (xactn/object oid/propertyId).  This should indeed be unique.  
> However, for a large xactn (in isis-app-todoapp) found certain circumstances when the "changedProperties" map (keyed by AdapterAndProperty) seems to hold entries that violate this constraint.
> Fix is to implement the hashCode/equals of AdapterAndProperty in a fashion in a more straightforward way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)