Hi Oscar, thanks for the quick response; within On 30 June 2014 08:00, GESCONSULTOR <[email protected]> wrote:
> Se has a similar use cases to this one, when an event should be published > when the user wanted to remove the domain object. > > We can publish the event (eventBus.post(...)) on the "removing" lifecycle > method. > > As it's executed in the context of the same transaction where we change > the references in all other objects, DN hasn't dispatched the delete > command, no references to deleted objects are kept on the database. > > Shouldn't it be enough for this case? Perhaps I'm missing something. > > This approach won't work, because we need to replace the reference with a different one. It's basically a 2cascade update" of the impacted objects. Dan > >
