[logback-dev] [JIRA] Commented: (LBCLASSIC-59) LogbackErrorListener

[Ceki Gulcu (JIRA)]

    [ http://jira.qos.ch/browse/LBCLASSIC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10850#action_10850 ] 

Ceki Gulcu commented on LBCLASSIC-59:
-------------------------------------

Szel,

You can register a status listener in a config file as follows:

 <configuration>  
  <statusListener   class="name.of.your.StatusListener" /> 
    ... the rest of the configuration file 
</configuration>

This feature was implemented in 0.9.10 but documented only in 0.9.12 .

> LogbackErrorListener
> --------------------
>
>                 Key: LBCLASSIC-59
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-59
>             Project: logback-classic
>          Issue Type: Improvement
>            Reporter: Anton Tagunov
>            Assignee: Logback dev list
>            Priority: Minor
>             Fix For: 0.9.10
>
>
> Presently we can only poll StatusManager for errors. It would be nice to be able to subscribe to these messages.
> One idea was to allow custom StatusManager implementations.
> This sounds like a nice and sane idea in its own right.
> However I feel that providing subscription to error events and allowing users to provide alternative StatusManager implementations are orthogonal concerns.
> In fact I feel that application should be able to subscribe to logback errors no matter what StatusManager is used stock or custom.
> In other words I suggest it to be part of StatusManager interface/contract to provide subscriptions.
> Which brings me back to the idea that it would be best to provide subscription (listener) facility in the standards StatusManager.
> On yet another account http://jira.qos.ch/browse/LBCLASSIC-58 may be enough for most practical users.
> And I suspect that the most common LogbackErrorListener implementation will simply log to System.out.
> In any case we badly need to get these errors out of Logback.
> BTW an alternative implemenation of LogbackListener might log to a file.

-- 
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