[jira] [Commented] (ISIS-865) Either warn or fail-fast if an action is annotated with safe semantics but nevertheless results in dirty objects in the xactn.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148202#comment-14148202 ] 

ASF subversion and git services commented on ISIS-865:
------------------------------------------------------

Commit a33021644049c1b2aef71623ce69ee6d98c9d1d0 in isis's branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a330216 ]

ISIS-865: checks if any (non-Command) objects have been dirtied in an xactn initiated by an action with safe-semantics; if so, and if "isis.persistor.ensureSafeSemantics" is "true", will abort xactn.

Whichever way setting, will log with ERROR severity.

NB: this feature requires a CommandService impl that supports the new Command2 API.

Also supported in integ tests.

The default is taken to be "false", ie only log error, don't abort xactn.  This is for backward compatibility with 1.6.0 and previous versions.


> Either warn or fail-fast if an action is annotated with safe semantics but nevertheless results in dirty objects in the xactn.
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-865
>                 URL: https://issues.apache.org/jira/browse/ISIS-865
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: core-1.6.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: core-1.7.0
>
>
> Following on/inspired by ISIS-864.
> Needs some discussion to decide on how to configure.  Warning could just be logging, while fail-fast could mean throw an exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)