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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ISIS-599:
------------------------------------------------------

Commit e0dd1c868f643734050fdf23a56c2ffbbc04cbe7 in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e0dd1c8 ]

ISIS-599: config property to enable logging in exception recognizers

Thus, if "isis.services.exceprecog.logRecognizedExceptions" set to true,
then a stack trace of any recognized exceptions will be logged.

If the exception is NOT recognized, then no stack trace is logged; the
assumption is that if none of the recognizers recognize the exception,
then it will bubble up and its stack trace be logged anyway as a
unexpected exception.

In addition:
- simplified the ExceptionRecognizer hierarchy
- made ExceptionRecognizers be init/shutdown via @PostConstruct methods etc
  (to read the configuration)
- updated the example isis.properties files for the archetypes.


> 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: Core, Objectstore: JDO
>    Affects Versions: objectstore-jdo-1.3.0, core-1.3.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 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)