[
https://issues.apache.org/jira/browse/SLING-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-3323:
---------------------------------
Description:
When things go wrong, a health check implementation should be able to
(optionally) add an exception to a result log entry. That way the exception
with its causes can be shown in a UI (e.g. the web console). The main benefits
are:
* The user in front of JMX or web console will always be technical and
therefore understand stack traces (and appreciate having this additional
information)
* If the exception cannot be added to the result, implementors can only use the
message of the exception and add it to the result message, thus losing all
exception root cause information (e.g. root causes are very important when
using a special framework stack like CXF/SOAP)
This is a reduced version of the proposal of in SLING-3302 that will not be
fixed.
was:
When things go wrong, a health check implementation should be able to
(optionally) add an exception to a result log entry. That way the exception
with its causes can be shown in a UI (e.g. the web console). The main benefits
are:
* The user in front of JMX or web console will always be technical and
therefore understand stack traces (and appreciate having this additional
information)
* If the exception is not added to the result, implementors can only use the
message of the exception and add it to the result message, thus loosing all
exception root cause information (e.g. root causes are very important when
using a special framework stack like CXF/SOAP)
This is a reduced version of the proposal of in SLING-3302 that will not be
fixed.
> Extend ResultLog.Entry to (optionally) hold an exception
> --------------------------------------------------------
>
> Key: SLING-3323
> URL: https://issues.apache.org/jira/browse/SLING-3323
> Project: Sling
> Issue Type: Improvement
> Components: Health Check
> Reporter: Georg Henzler
> Attachments: SLING-3323-result-log-entry-with-optional-exception.patch
>
>
> When things go wrong, a health check implementation should be able to
> (optionally) add an exception to a result log entry. That way the exception
> with its causes can be shown in a UI (e.g. the web console). The main
> benefits are:
> * The user in front of JMX or web console will always be technical and
> therefore understand stack traces (and appreciate having this additional
> information)
> * If the exception cannot be added to the result, implementors can only use
> the message of the exception and add it to the result message, thus losing
> all exception root cause information (e.g. root causes are very important
> when using a special framework stack like CXF/SOAP)
> This is a reduced version of the proposal of in SLING-3302 that will not be
> fixed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
