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 2017/02/12 22:48:41 UTC

[jira] [Commented] (ISIS-1576) Command for action that throws an exception does not flag that it failed.

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

Dan Haywood commented on ISIS-1576:
-----------------------------------

OK, so the reason for this is that recoverable exceptions (eg subclasses of org.apache.isis.applib.RecoverableException) are not treated as failed commands.  The exception is converted into a message to display to the end user, but then a new xactn is started to persist the command.

Have decided not to fix.

> Command for action that throws an exception does not flag that it failed.
> -------------------------------------------------------------------------
>
>                 Key: ISIS-1576
>                 URL: https://issues.apache.org/jira/browse/ISIS-1576
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.13.2.1
>            Reporter: Dan Haywood
>            Priority: Minor
>             Fix For: 1.14.0
>
>
> that is, the exception flag is not being set, the stacktrace is not being captured.
> One way to reproduce: 
> - run Estatio-ECP, 
>   - but comment out DocFragmentData#InvoiceDescription_DemoGbr so this info is missing.
> - Invoices > Calculate, select OXF-MEDIAX-002
> - on resultant InvoiceRun, select the Invoice just created
> - Approve the invoice
>   - creates a command, and corresponding published interaction event
> - attempt to Invoice the invoice
>   - throws an exception
>   - the command is persisted ... but does not indicate it failed
>   - there is no corresponding published interaction event.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)