karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2238) Logback appender
Date Fri, 15 Mar 2013 11:12:12 GMT

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

Guillaume Nodet commented on KARAF-2238:
----------------------------------------

Did you experiment with paxlogging ? The threading issues have been fixed in the custom version
of log4j which is embedded.

For custom appenders, paxlogging has a dedicated api you can use so that it's independant
of the backend being log4j or logback.
                
> 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

Mime
View raw message