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 A72BA9C8D for ; Mon, 23 Apr 2012 12:25:43 +0000 (UTC) Received: (qmail 9362 invoked by uid 500); 23 Apr 2012 12:25:43 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 9331 invoked by uid 500); 23 Apr 2012 12:25:43 -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 9322 invoked by uid 99); 23 Apr 2012 12:25:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 12:25:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bengt.rodehav@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 12:25:28 +0000 Received: by lahe6 with SMTP id e6so10477332lah.32 for ; Mon, 23 Apr 2012 05:25:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=pORBsmPD9n0L0DSCMEsj/Frpje6Gb35NWXz+7zrSFoY=; b=a6vr1dpS5G61KG7/B2vSNUdnK6U9gnfT5Qp3DtCTQi2fij5Wtdrb/d0TWq1tG+OWUc F6AHVylFMXT+YNxpVwU7hB1M6Fm7GObDa5XWF4XoL6vYmCJl0g0GRXG5eBiMVIQmEX3J 9r8KjwRZ8WlyoWAmLI8EwqyYWSB01e5FUwAQ6HohINDLbZLwSSd6We5483rJXsL1V6z3 pdW4T7DASW2iBstq94re9EWSDfKG8/qAfuioFXaEsDMZgBYenyXqwx0UAO9B0P4nUG+L 7mZ9wU1LB4guTwoE5xKp/7kpjO8mQCyWvvTwq9LVV7P25MvX9Wmw0XnjQ0EJNnAV/mtU ayuA== MIME-Version: 1.0 Received: by 10.112.103.202 with SMTP id fy10mr7587862lbb.43.1335183906377; Mon, 23 Apr 2012 05:25:06 -0700 (PDT) Sender: bengt.rodehav@gmail.com Received: by 10.152.24.74 with HTTP; Mon, 23 Apr 2012 05:25:06 -0700 (PDT) In-Reply-To: <4F954491.9000306@nanthrax.net> References: <4F9512DC.80004@nanthrax.net> <4F9529B6.8080707@nanthrax.net> <4F954491.9000306@nanthrax.net> Date: Mon, 23 Apr 2012 14:25:06 +0200 X-Google-Sender-Auth: 5CbFggwBFmVa_xLM97_7Ac3j3Cg Message-ID: Subject: Re: Problems with Camel's Karaf commands From: Bengt Rodehav To: users@camel.apache.org Content-Type: multipart/alternative; boundary=f46d0401f91d7311a404be57ba8f --f46d0401f91d7311a404be57ba8f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I appreciate it JB, Will all functionality be available even when looking up via JMX? /Bengt 2012/4/23 Jean-Baptiste Onofr=E9 > Hi Bengt, > > JMX is only used for statistic. The purpose is to be able to display and > manage routes without the JMX layer (without the management feature > installed). > > However, we can have a dual handling, with an option to choose to lookup > by OSGi services or JMX. > > I will implement an enhancement on trunk for that. > > Regards > JB > > > On 04/23/2012 01:52 PM, Bengt Rodehav wrote: > >> OK - that explains it. I have no camel context published as OSGi service= . >> Is this something I should do in order to "integrate" with the Camel Kar= af >> commands? >> >> Why isn't JMX used? (It seems to work fine under Karaf) What are the ext= ra >> benefits from *not* using JMX? >> >> >> If I publish all my camel contexts as OSGi services, will they then be >> visible to the Karaf commands? >> >> /Bengt >> >> 2012/4/23 Jean-Baptiste Onofr=E9 >> >> Hi Bengt, >>> >>> I'm gonna take a look but the Karaf commands are based on Camel Context >>> registered as OSGi service. Could you take a look about the services >>> available (using ls command in Karaf shell). >>> >>> Regards >>> JB >>> >>> >>> On 04/23/2012 11:01 AM, Bengt Rodehav wrote: >>> >>> Hello JB, >>>> >>>> I use Java DSL. I create multiple camel contexts with code like this: >>>> >>>> *** >>>> >>>> **CamelContextFactory contextFactory =3D new CamelContextFactory(); >>>>> **contextFactory.****setBundleContext(****theBundleContext); >>>>> **CamelContext context =3D contextFactory.createContext()****;* >>>>> >>>>> >>>> >>>> The contexts and routes work perfectly well and I can also access them >>>> via >>>> JMX from JConsole but I cannot see them using the Karaf commands. >>>> >>>> /Bengt >>>> >>>> 2012/4/23 Jean-Baptiste Onofr=E9 >>>> >>>> Hi Bengt, >>>> >>>>> >>>>> which DSL do you use ? >>>>> Do you use an "OSGi" complient camel context if you do it >>>>> programmatically >>>>> ? >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> >>>>> On 04/23/2012 10:27 AM, Bengt Rodehav wrote: >>>>> >>>>> I'm using Camel 2.9.1 and Karaf 2.2.5. >>>>> >>>>>> >>>>>> I have several Camel contexts and several routes running. Using >>>>>> JConsole I >>>>>> can see the contexts, routes and other JMX information. >>>>>> >>>>>> However, if I use the Camel commands from within the Karaf console I >>>>>> see >>>>>> nothing. E g the command "camel:context-list" shows nothing. >>>>>> >>>>>> Is this a bug or am I doing something wrong? >>>>>> >>>>>> /Bengt >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>> Jean-Baptiste Onofr=E9 >>>>> jbonofre@apache.org >>>>> http://blog.nanthrax.net >>>>> Talend - http://www.talend.com >>>>> >>>>> >>>>> >>>> -- >>> Jean-Baptiste Onofr=E9 >>> jbonofre@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >>> >> > -- > Jean-Baptiste Onofr=E9 > jbonofre@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > --f46d0401f91d7311a404be57ba8f--