[jira] [Updated] (ISIS-665) ObjectActionImpl should escalate a thrown Isis ApplicationException to its underlying cause if the transaction is in a state of mustAbort.

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

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

Dan Haywood updated ISIS-665:
-----------------------------

    Fix Version/s: archetype-quickstart-wrj-1.4.0

> ObjectActionImpl should escalate a thrown Isis ApplicationException to its underlying cause if the transaction is in a state of mustAbort.
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-665
>                 URL: https://issues.apache.org/jira/browse/ISIS-665
>             Project: Isis
>          Issue Type: Improvement
>          Components: Archetype: ToDoApp WRJ, Core, Objectstore: JDO
>    Affects Versions: archtype-quickstart-wrj-1.3.1, objectstore-jdo-1.3.0, core-1.3.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: archetype-quickstart-wrj-1.4.0, objectstore-jdo-1.4.0, core-1.4.0
>
>
> We hit a situation whereby a bug in the domain code was causing a JDOUserException to be thrown (missing a mandatory-field), but then throwing an org.apache.isis.applib.ApplicationException.  
> This exception is only intended for non-fatal exceptions.  Isis therefore attempted to commit the transaction subsequently only to find it had already been aborted.
> ObjectActionImpl should try to identify this programming error, and "do the right thing", which is probably to throw the ApplicationException's underlying cause (else a runtime exception if there is none).
> NB: this ticket should also include adding some documentation to the website, since this is a pretty subtle issue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)