Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B91CD10AB8 for ; Mon, 31 Mar 2014 19:31:08 +0000 (UTC) Received: (qmail 15255 invoked by uid 500); 31 Mar 2014 19:31:07 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 15080 invoked by uid 500); 31 Mar 2014 19:31:06 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 15065 invoked by uid 99); 31 Mar 2014 19:31:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2014 19:31:05 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of gr.grzybek@gmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2014 19:31:01 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WUhuq-0006W8-Kc for users@camel.apache.org; Mon, 31 Mar 2014 12:30:40 -0700 Date: Mon, 31 Mar 2014 12:30:40 -0700 (PDT) From: Grzegorz Grzybek To: users@camel.apache.org Message-ID: <1396294240619-5749575.post@n5.nabble.com> In-Reply-To: References: <1377769049921-5738205.post@n5.nabble.com> <1377874733881-5738319.post@n5.nabble.com> Subject: Re: Logging into the bundle log file via to("log:...") MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello I did some investigation and I think it's almost impossible to properly set the bundle in org.ops4j.pax.logging.slf4j.Slf4jLogger which is used by CamelLogger. The problem is described here . org.ops4j.pax.logging.internal.BundleHelper always finds the camel-core bundle as the one which requests creating Logger. So either we introduce a way of configuring org.ops4j.pax.logging.internal.BundleHelper (by setting a filter or number of traces in stacktrace) or we could just use user provided (in message headers) Logger instance and use it in org.apache.camel.processor.CamelLogProcessor.process(**) methods. We could use org.apache.camel.util.CamelLogger.log() methods which take Logger parameter (if appropriate object is found in headers. What do you think? regards Grzegorz Grzybek -- View this message in context: http://camel.465427.n5.nabble.com/Logging-into-the-bundle-log-file-via-to-log-tp5738205p5749575.html Sent from the Camel - Users mailing list archive at Nabble.com.