[CAUSEWAY-534] Does JDO Objectstore ever need to create DataNucleusUpdateObjectCommand commands?

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: core-1.2.0
• Fix Version/s: 1.10.0
• Component/s: Core
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 15/Sep/13 10:39
• Updated: 10/Nov/15 07:00
• Resolved: 26/Oct/15 11:24

Description

Following on from ISIS-533, I'm not sure there's ever any reason for the DataNucleusUpdateObjectCommand to do anything, therefore for it to be created. The Isis core can, instead, merely rely upon DN's built-in object dirtying.

This ticket is to explore this issue and perhaps to make the objectChanged() method - that creates the Update command - into a no-op if the JDO objectstore is configured.

Issue Links

• is part of: CAUSEWAY-1194 Remove dead code, remove support for @Aggregated, for isDirty/clearDirty/markDirty.