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 2013/11/21 18:28:36 UTC

[jira] [Updated] (ISIS-599) Better message and diagnostics for Exception Recognizers

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

Dan Haywood updated ISIS-599:
-----------------------------

    Component/s: Archetype: ToDoApp WRJ
                 Archetype: Simple WRJ

> Better message and diagnostics for Exception Recognizers
> --------------------------------------------------------
>
>                 Key: ISIS-599
>                 URL: https://issues.apache.org/jira/browse/ISIS-599
>             Project: Isis
>          Issue Type: Improvement
>          Components: Archetype: Simple WRJ, Archetype: ToDoApp WRJ, Core, Objectstore: JDO
>    Affects Versions: archetype-simple-wrj-1.3.1, 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-simple-wrj-1.4.0, archetype-quickstart-wrj-1.4.0, objectstore-jdo-1.4.0, core-1.4.0
>
>
> When a registered ExceptionRecognizer recognizes an exception, it parses the exception message and returns a user-friendly message to display.  Nothing is logged.
> Currently the parsed message returned is parsed from the outer-most exception; for better information it should instead parse the root cause.
> For the developer, it would be useful for the exceptions to be logged.  One way to do this might be to make them logged if running in prototype mode, but not logged otherwise.



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