You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/10/08 00:39:33 UTC
[jira] [Resolved] (ISIS-864) Command should be persisted if any
dirty objects enlisted into transaction, in order to ensure no accidental
orphans.
[ https://issues.apache.org/jira/browse/ISIS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood resolved ISIS-864.
------------------------------
Resolution: Fixed
> Command should be persisted if any dirty objects enlisted into transaction, in order to ensure no accidental orphans.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-864
> URL: https://issues.apache.org/jira/browse/ISIS-864
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.6.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.7.0
>
>
> adding:
> isis.services.command.actions=ignoreQueryOnly
> means that commands are not persisted for any query-only actions. But that means that if an action is incorrectly annotated with query-only semantics (ie @ActionSemantics(Of.SAFE)) and then dirties objects, then we can end up with audit entries for those dirty objects that are orphaned.
> So, this enhancement is for Isis core to always persist a command whenever an object has been dirtied, even if from an action that has SAFE semantics.
> then
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)