[
http://jira.qos.ch/browse/LBCORE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11803#action_11803
]
Ceki Gulcu commented on LBCORE-159:
-----------------------------------
Interesting approach to a non-trivial problem. The approach taken in
logback-audit exposes the exceptions in the audit-logging API which is quite
different than the logging API.I kind of like your way.
> AppenderBase and UnsynchronizedAppenderBsae do not allow exceptions to
> percolate to the application
> ---------------------------------------------------------------------------------------------------
>
> Key: LBCORE-159
> URL: http://jira.qos.ch/browse/LBCORE-159
> Project: logback-core
> Issue Type: Improvement
> Components: Appender
> Affects Versions: 0.9.24
> Environment: All
> Reporter: Ralph Goers
> Assignee: Ceki Gulcu
> Attachments: exceptionPatch.txt
>
>
> When logging some events the application needs to be informed that the
> publishing of the event failed. Currently, AppenderBase and
> UnsynchronizedAppenderBase catch and handle all exceptions making it
> impossible to use any of the out-of-the box Logback appenders in these
> situations. This is particularly important when performing auditing and
> sending the events to a database, JMS queue, socket, etc. as the application
> would want to fail the current operation if it cannot be audited.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
