[jira] [Resolved] (SLING-4907) Provide support for registering Filter with all configured appenders

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra resolved SLING-4907.
------------------------------------
    Resolution: Fixed

If the {{Filter}} {{appenders}} property is set {{*}} then that filter would be registered against all Appenders

{code}
        Dictionary<String, Object> props = new Hashtable<String, Object>();
        props.put("appenders", "*");
        ServiceRegistration sr  = bundleContext.registerService(Filter.class.getName(), stf, props);
{code}

Implemented in http://svn.apache.org/r1692823

> Provide support for registering Filter with all configured appenders
> --------------------------------------------------------------------
>
>                 Key: SLING-4907
>                 URL: https://issues.apache.org/jira/browse/SLING-4907
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: Commons Log 4.0.4
>
>
> Current Logback support provides support for registering {{Filter}} as OSGi services [1]. This only supports registering against known appenders. 
> If we need to have a logic which needs to handle/listen to all WARN and above log messages that needs to get logged then only way for now is to register a {{TurboFilter}} which has performance cost. To support such cases the {{Filter}} support should enable registering a Filter instance against all configured appenders. This would allow such a Filter to listen to all logged messages without the performance cost
> [1] https://sling.apache.org/documentation/development/logging.html#filters-as-osgi-services



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)