You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Gareth Collins (JIRA)" <ji...@apache.org> on 2013/06/20 21:50:20 UTC

[jira] [Commented] (KARAF-2238) Logback appender

    [ https://issues.apache.org/jira/browse/KARAF-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689562#comment-13689562 ] 

Gareth Collins commented on KARAF-2238:
---------------------------------------

PaxAppender does not get passed markers, does it (markers are only supported by logback and log4j 2)?
                
> Logback appender
> ----------------
>
>                 Key: KARAF-2238
>                 URL: https://issues.apache.org/jira/browse/KARAF-2238
>             Project: Karaf
>          Issue Type: Improvement
>            Reporter: Keren Dong
>
> Can we have logback as the default logging implementation of pax-logging-service and have a way to load custom appender?
> We want to create a log appender with custom threading control and found that we can't with log4j 1.x (https://issues.apache.org/jira/browse/LOG4J2-3). Karaf's pax-logging-service uses (slf4j+log4j), so we replaced pax-logging-logback. But we find it difficult to do because pax-logging-logback embeds Logback jars inside the bundle without exporting packages and faced with osgi class loading issues. We can do it by defining custom appender fragment for pax-logging-logback host at startup.properties and set the org.ops4j.pax.logging.cfg for logback configuration. But we find that is not convenient for development for having to copy updated Jars to <kavaf_home>/system folder in every iteration.
> We are wondering if there is better way dynamically add the appender when we install our bundle on a standard Karaf distribution?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira