commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SCXML-184) Allow subclasses of SimpleErrorReporter to override the current and only logging handling
Date Fri, 13 Dec 2013 01:06:10 GMT

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

Ate Douma closed SCXML-184.
---------------------------

    Resolution: Fixed

Subclasses now can override/extend the following SimpleErrorReporter method:

    protected void handleErrorMessage(final String errorCode, final String errDetail, final
Object errCtx, final CharSequence errorMessage);


> Allow subclasses of SimpleErrorReporter to override the current and only logging handling
> -----------------------------------------------------------------------------------------
>
>                 Key: SCXML-184
>                 URL: https://issues.apache.org/jira/browse/SCXML-184
>             Project: Commons SCXML
>          Issue Type: Improvement
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>            Priority: Minor
>             Fix For: 2.0
>
>
> Currently the SimpleErrorReporter first evaluates the error condition and builds up a
detailed message, and finally writes it to the log (if warnEnabled).
> To allow more control and further usage of the resulting detailed message by subclasses
I'm going to move the final step, logging the message, to a separate (protected) handleErrorMessage
method.
> So the behavior of SimpleErrorReporter itself won't change, but subclasses now can do
something extra/meaningful beyond mere logging with the error message.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message