[
https://issues.apache.org/jira/browse/LOG4NET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-394:
-----------------------------------
Fix Version/s: (was: 1.3.0)
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
> Assignee: Dominik Psenner
> 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
(v6.1#6144)
