[jira] [Closed] (ISIS-758) Auditing should be able to cope with a change to a property where the referenced object has been deleted.

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

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

Dan Haywood closed ISIS-758.
----------------------------


> Auditing should be able to cope with a change to a property where the referenced object has been deleted.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-758
>                 URL: https://issues.apache.org/jira/browse/ISIS-758
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: core-1.4.0
>            Reporter: Jeroen van der Wal
>            Assignee: Dan Haywood
>             Fix For: core-1.5.0
>
>
> For example, doing a "cascade" delete of Parent <->* Child.
> Here, the Parent and each of the Children will be audited, and in the case of Child, its "parent" reference is changing from (parent) to null.  
> However, as the parent itself is deleted, trying to generate its toString() (when using JDO object store) is causing an exception.
> The fix is to grab the toString of the object when the objects are enlisted into the transaction, before they are deleted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)