[jira] [Closed] (ISIS-449) Error handling when transaction aborted incorrect

["Dan Haywood (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ISIS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood closed ISIS-449.
----------------------------


> Error handling when transaction aborted incorrect
> -------------------------------------------------
>
>                 Key: ISIS-449
>                 URL: https://issues.apache.org/jira/browse/ISIS-449
>             Project: Isis
>          Issue Type: Bug
>          Components: Core, Viewer: Wicket
>    Affects Versions: viewer-wicket-1.2.0, core-1.2.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: viewer-wicket-1.3.0, core-1.3.0
>
>
> Situation was as follows:
> - two edits made that would cause a unique index constraint violation in the database, and the other that (due to a programming bug) would cause a null pointer.
> In IsisTransactionManager#endTransaction(), the abortCause gets set onto the IsisTransaction because of the unique constraint, causing Isis to attempt call abortTransaction().  However, there is no exception handling around this method, and a subsequent NPE is not captured for rendering.
> In addition, in the wicket viewer, whenever an exception does occur and the transaction is aborted, the attempt to redirect to the error page will fail if the page requires a transaction.  A new transaction should therefore be started.



--
This message was sent by Atlassian JIRA
(v6.1#6144)