[CAUSEWAY-758] Auditing should be able to cope with a change to a property where the referenced object has been deleted.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: core-1.4.0
• Fix Version/s: core-1.5.0
• Component/s: Core
• Assignee: Daniel Keir Haywood
• Reporter: Jeroen van der Wal
• Created: 02/Apr/14 12:56
• Updated: 09/Jun/14 23:25
• Resolved: 03/Apr/14 09:43

Description

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.