[CAUSEWAY-2423] Persisted callback and PublisherService#changedObjects are not called, instead appear as updates.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0-M3
• Fix Version/s: 2.0.0-M4
• Component/s: Core
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 21/Aug/20 07:23
• Updated: 04/Oct/20 14:20
• Resolved: 04/Oct/20 11:16

Description

Due to use of EntityUtil.isAttached(...) in the PersistenceSession5#enlistCreated... method, rather than checking our own Oid.  In this particular case they were not equivalent.

Fix:

• was able to simplify and remove some redundant code, using instead

persistable.dnGetStateManager().isNew(persistable)

as the mechanism to determine in preStore/postStore whether we are dealing within an insert or an update.

Issue Links

• is related to: CAUSEWAY-2441 Auditing/Publishing: dispatch calls happen before enlist calls