You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@causeway.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2023/03/18 10:44:00 UTC

[jira] [Closed] (CAUSEWAY-3369) Remove the causeway.extensions.commandlog.publish-policy (ONLY_IF_SYSTEM_CHANGED)

     [ https://issues.apache.org/jira/browse/CAUSEWAY-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Keir Haywood closed CAUSEWAY-3369.
-----------------------------------------

> Remove the causeway.extensions.commandlog.publish-policy (ONLY_IF_SYSTEM_CHANGED)
> ---------------------------------------------------------------------------------
>
>                 Key: CAUSEWAY-3369
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-3369
>             Project: Causeway
>          Issue Type: Improvement
>          Components: Extensions CommandLog
>    Affects Versions: 2.0.0-M9
>            Reporter: Daniel Keir Haywood
>            Assignee: Daniel Keir Haywood
>            Priority: Major
>             Fix For: 2.0.0-RC1
>
>
> This feature only works if audit trail is enabled, which is very rather subtle to miss.  And in any case, there's value in recording all commands by default, not just those that are for non-safe actions.
> Also - and where this originated fro - this is a prereq to CAUSEWAY-3366; which extends the commandlog to persist commands even before they are completed (this then allows domain entities to have referneces/FKs to CommandLogEntry).  It was always rather odd that a command is only ever persisted at the end when it is _meant_ to represent the intention to invoke an action, ie conceptually is known about "before-hand".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)