camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Camel Log4j Appender
Date Thu, 14 Apr 2011 12:49:52 GMT
Yeah this can be tricky as you would have different classloaders and whatnot.
Also the log4j could be shared among different Camel applications.

You can use a remote transport of some sort, and send data over HTTP.

However if you run in Karaf, then pax-logging, may have some osgi
related stuff you can leverage.

On Thu, Apr 14, 2011 at 2:17 PM, Gert Villemos <> wrote:
> Creating a custom log4j appender is very easy (... indeed we have one but we
> are not happy with it as it only injects into ActiveMQ and not into a Camel
> route).
> Our only problem (and this is now turning into a developer question more
> than a user question) is how can the custom Appender which is a part of the
> log4j hierarchy get a reference to a route producer template?
> If we for example
> 1. Configure an instance of the custom appender and using the
> / log4j.xml file configure it to inject into the route
> "direct:logs".
> 2. Configure a Camel route 'from("direct:logs").to("activemq:topic:logs)'
> How do we in the log4j Appender get a reference to the ProducerTemplate with
> the identifier 'direct:logs'?
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
CamelOne 2011:
Twitter: davsclaus
Author of Camel in Action:

View raw message