[
https://issues.apache.org/jira/browse/ISIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161602#comment-14161602
]
ASF subversion and git services commented on ISIS-865:
------------------------------------------------------
Commit 52c18eb8b31fde5bb977bfca72ddeb323413e0be in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=52c18eb ]
ISIS-865: further fixes for 'ensureSafeSemantics'; also ensure that integration
tests' command are set to be executed as "USER" (rather than "OTHER").
The further fixes for 'ensureSafeSemantics' are mostly comments; the actual fix
was in the todo integration tests that were failing because of a missing call
to 'nextTransaction()'. There is a bit more 'belt-n-braces' resetting to null:
- of the command's event (at xactn completion)
- of the xactn's changedProperties hash (at xactn completion)
> 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)
