In case you deploy camel in karaf, camel already defines a custom
pax-logging appender which intercepts all log events (slf4j, log4j,
jul, jcl) and can process them.
See http://camel.apache.org/pax-logging.html
On Thu, Apr 14, 2011 at 14:49, Claus Ibsen wrote:
> Yeah this can be tricky as you wou
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 yo
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
On Thu, Apr 14, 2011 at 1:27 PM, Gert Villemos wrote:
> Did this issue moved forward?
>
> I can find a log4j JMS logger that can inject data into an ActiveMQ, but I
> would like to inject events into a camel route which might go to ActiveMQ,
> but might also have other steps.
>
> Can this be done?
Did this issue moved forward?
I can find a log4j JMS logger that can inject data into an ActiveMQ, but I
would like to inject events into a camel route which might go to ActiveMQ,
but might also have other steps.
Can this be done?
--
View this message in context:
http://camel.465427.n5.nabble.
