Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 22735 invoked from network); 4 Mar 2009 14:33:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Mar 2009 14:33:14 -0000 Received: (qmail 76625 invoked by uid 500); 4 Mar 2009 14:33:13 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 76605 invoked by uid 500); 4 Mar 2009 14:33:13 -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 76591 invoked by uid 99); 4 Mar 2009 14:33:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 06:33:13 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com designates 209.85.198.240 as permitted sender) Received: from [209.85.198.240] (HELO rv-out-0708.google.com) (209.85.198.240) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 14:33:06 +0000 Received: by rv-out-0708.google.com with SMTP id c5so3598972rvf.56 for ; Wed, 04 Mar 2009 06:32:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=c0NQu616RK+cfVnQwpplIBvfk3oWhS6b/XO1sk6uZi4=; b=LW2LS0EgWHetcuaxRO2Qe2zDGwL6btX/WSqrb2lsF3GoaCbEKT2hoJWqfI69TTVU38 tIBsGtrAZjwdOvOSr37g22gdA7KkkQBg+d5R+kFGbJdqGpmU53bgiwFrsJWVWEpky/Y8 gd5jiMXoMc+eqvEVZPzNnbuiOTUIgOLPacw8s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=eh/5lbG+OE5dnONmUcxsstlIOhjQyMFkiZgm9rLnuBrhpOHDcunaL0YECG+26L5vIp 83RhlokMvVPPQ/t0/ZegvAT7tfwL/r7rXXvRpYNr+ORniJfLk6mCFNjJbWEBVdG9JVmI h1IF3CyV3IgH6Ooag1tCC51cg6Eym2Z0w72RU= MIME-Version: 1.0 Received: by 10.141.96.19 with SMTP id y19mr4188419rvl.201.1236177165694; Wed, 04 Mar 2009 06:32:45 -0800 (PST) In-Reply-To: <22330735.post@talk.nabble.com> References: <22330735.post@talk.nabble.com> Date: Wed, 4 Mar 2009 22:32:45 +0800 Message-ID: Subject: Re: camel osgi tracing in spring dsl does not work - 2.0 SNAPSHOT From: Willem Jiang To: users@camel.apache.org Content-Type: multipart/alternative; boundary=000e0cd1a8e4d7383804644bec34 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd1a8e4d7383804644bec34 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Does it work in a no osgi environment ? Willem On Wed, Mar 4, 2009 at 10:10 PM, cmoulliard wrote: > > Hi, > > It seems that the tracing does not work when activated like this in an > camel > osgi spring dsl route ? > > > > > org.apache.camel.example.reportincident.routing > > uri="file://d:/temp/data/?moveExpression=d:/temp/done/${file:name}" /> > > > > > > > type="org.apache.camel.example.reportincident.domain.InputReportIncident" > /> > > > OK > > > > > > Version affected : 2.0-SNAPSHOT > > Regards, > > > ----- > Charles Moulliard > SOA Architect > > My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ > -- > View this message in context: > http://www.nabble.com/camel-osgi-tracing-in-spring-dsl-does-not-work---2.0-SNAPSHOT-tp22330735p22330735.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > --000e0cd1a8e4d7383804644bec34--