Hi
Yeah wonder if we could improve this in Camel, so .to("log:xxx") and
.log("foo") uses a logger created by the application bundle.
So if we let the application bundles classloader try to load the
logger as a class, and use that? Well we could try to experiment. Then
by default it still runs normally for end users, but for ppl using
that shift appender then the pax-logger framework may be able to
figure out the logger class is from the application bundle, and not
from camel-core bundle.
On Fri, Aug 30, 2013 at 5:03 PM, Raul Kripalani <r...@evosent.com> wrote:
> If you use the logging API directly (e.g. slf4j) from within a Processor,
> it should. But that's not the Camel way of doing things ;-)
>
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Fri, Aug 30, 2013 at 3:58 PM, Hilderich <hilde.sch...@yahoo.de> wrote:
>
>> Hello Raul,
>>
>> as you can see below I am using the bundle name as the sifting key:
>>
>> As you have mentioned I have no hope that plain logging inside the route
>> can
>> appear in
>> the proper bundle log file, isn't it?
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Logging-into-the-bundle-log-file-via-to-log-tp5738205p5738319.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
