logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4NET-394) Lambda-based ILog-Extensions should catch errors
Date Fri, 04 Oct 2013 09:15:42 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786013#comment-13786013

Dominik Psenner edited comment on LOG4NET-394 at 10/4/13 9:14 AM:

Agreed. I'll look into patching this so that it will be in 1.2.13.

was (Author: nachbarslumpi):
Agreed. I'll look into patchting this so that it will be in 1.2.13.

> Lambda-based ILog-Extensions should catch errors
> ------------------------------------------------
>                 Key: LOG4NET-394
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-394
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.12
>            Reporter: Gian Marco Gherardi
>            Priority: Minor
>             Fix For: 1.2.13
> The new lambda syntax introduced with LOG4NET-290 allow wrapping log related code in
a lambda to be executed only if necessary. In the log4net spirit of being a reliable logging
system (see http://logging.apache.org/log4net/release/faq.html) also the log related code
contained in the lambda should not block application by throwing exception and so the lambda
execution shluld be wrapped in a try...catch

This message was sent by Atlassian JIRA

View raw message