[
https://issues.apache.org/jira/browse/ISIS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526454#comment-15526454
]
ASF subversion and git services commented on ISIS-1498:
-------------------------------------------------------
Commit 853405172c57ebbe6f4cbef98ab1e5c3e02a9aca in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8534051 ]
ISIS-1498: introduces new clearAbortCauseAndContinue() internal API for
IsisTransaction, and leverage within BackgroundCommandExecution for the case
where an action throws an exception (want to capture that, mark on the
background Command, and persist).
> BackgroundCommandExecution does not handle exceptions correctly.
> ----------------------------------------------------------------
>
> Key: ISIS-1498
> URL: https://issues.apache.org/jira/browse/ISIS-1498
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.13.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.1
>
>
> Seen two separate issues.
> First, when there was a mismatch in arguments to parameters (see ISIS-1497),
> this resulted in an NPE in this line of the catch block:
> {code}
> Exception unused = backgroundInteraction.getPriorExecution().getThrew();
> {code}
> specifically, getPriorExecution() returned null.
> Then, when I worked around that issue so that the action could be invoked but
> when executed threw an exception, resulted in an NPE in this line of the
> catch block:
> {code}
> backgroundInteraction.getCurrentExecution().setThrew(e);
> {code}
> Here, getCurrentExecution() returned null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
