[
https://issues.apache.org/jira/browse/ISIS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957721#comment-13957721
]
ASF subversion and git services commented on ISIS-758:
------------------------------------------------------
Commit 8c45cc01b16cc95474894dc1a1033871a7e56500 in isis's branch
refs/heads/master from [~jcvanderwal]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8c45cc0 ]
ISIS-758: auditing should handle deleted objects.
Also:
- better exception handling within ObjectContracts for getValueOf(...).
> 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.4.2
>
>
> 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)
