[
https://issues.apache.org/jira/browse/ISIS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173706#comment-14173706
]
ASF subversion and git services commented on ISIS-864:
------------------------------------------------------
Commit f89e1e6279136529f87f244060b28c673275e529 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f89e1e6 ]
ISIS-864: guard to NOT persist commands if objects are dirtied as side-effect
of 'seed' services (as Estatio and the security module both use).
> 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)
