[
https://issues.apache.org/jira/browse/ISIS-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-3324:
--------------------------------------
Description:
as per this thread:
[https://the-asf.slack.com/archives/CFC42LWBV/p1673865917081639]
Seems that the code to fire the `persisted()` callback etc doesn't run if
`entity-change-publishing` is disabled. Whereas in fact, we should always call
these callbacks.
Problem noted against JDO, but quite possibly also present for JPA and so
should check for both.
was:
as per this thread:
[https://the-asf.slack.com/archives/CFC42LWBV/p1673865917081639]
We probably need a regression test for this, once fixed, to prevent
reoccurrence.
> Entity lifecycle callbacks should fire irrespective of the
> `entity-change-publishing` default.
> ----------------------------------------------------------------------------------------------
>
> Key: ISIS-3324
> URL: https://issues.apache.org/jira/browse/ISIS-3324
> Project: Isis
> Issue Type: Bug
> Components: Isis Persistence JDO
> Affects Versions: 2.0.0-M9
> Reporter: Daniel Keir Haywood
> Priority: Major
> Fix For: 2.0.0-RC1
>
>
> as per this thread:
> [https://the-asf.slack.com/archives/CFC42LWBV/p1673865917081639]
> Seems that the code to fire the `persisted()` callback etc doesn't run if
> `entity-change-publishing` is disabled. Whereas in fact, we should always
> call these callbacks.
> Problem noted against JDO, but quite possibly also present for JPA and so
> should check for both.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
