Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 23204 invoked from network); 23 Jan 2008 17:49:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2008 17:49:12 -0000 Received: (qmail 37654 invoked by uid 500); 23 Jan 2008 17:49:02 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 37582 invoked by uid 500); 23 Jan 2008 17:49:02 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 37573 invoked by uid 99); 23 Jan 2008 17:49:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2008 09:49:02 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com designates 64.233.170.184 as permitted sender) Received: from [64.233.170.184] (HELO rn-out-0102.google.com) (64.233.170.184) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2008 17:48:36 +0000 Received: by rn-out-0102.google.com with SMTP id i19so82283rng.2 for ; Wed, 23 Jan 2008 09:48:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=CbW9nn047s/AL8bQGkND5WmyYTmqg45Egt5H99K030Y=; b=mHuGP9lnyTuqt12LYgg1jXb07na9v8sT0+TvdFIZfVHpeCHjbVmXAEvOkEqh8rlYUst/YBUhrs6mjQkD1ZdwDV+OUALMT2PraTk0BS5526+1RBJCgjxQOMDZqvemZnB+M1r9AVGCw4mmj2uoTuqepuBaxtSwM1Vkbia79ppLdMw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=wTnOTQakUdBDpNtA4tghs5kbijpPe1J9ECulsqew04rkYJBU0RicMYtL8PYnnn47oc1+6211bj1/R1A7Kd73E9huKfcbms2mS6alytf2+SdAthk5aR+lObCKVOyr37AVr5NWWEBrFj2urb7e6r1vG+KsYqA4t+7sVLWeDJkLcgE= Received: by 10.150.212.14 with SMTP id k14mr3642498ybg.148.1201110521337; Wed, 23 Jan 2008 09:48:41 -0800 (PST) Received: by 10.150.148.20 with HTTP; Wed, 23 Jan 2008 09:48:41 -0800 (PST) Message-ID: Date: Wed, 23 Jan 2008 17:48:41 +0000 From: "James Strachan" To: camel-user@activemq.apache.org Subject: Re: what is best way to manage multiple camel contexts In-Reply-To: <15047497.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <15047497.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org On 23/01/2008, tieying Liu wrote: > > Hi: > > I am trying to find a way to dynamically start/stop/deploy/update multi > camel contexts using a web admin console and maybe groovy. Has anyone done > this already? I've done something kinda similar; using the ServiceMix MicroKernel you can hot deploy OSGi bundles (which are basically jars) and can contain Camel routing rules, a Spring XML and so forth. http://servicemix.apache.org/kernel/ Using the console you can start/stop bundles; it'd be trivial to add a Groovy based console for doing the same kinda thing. Or you can just edit, say a spring.xml or edit classes and have your IDE recompile them on the fly & update the .class files to have the bundles hot redeployed etc. So kinda similar to what you're suggesting, just implemented a slightly different way. The nice thing is this approach deals nicely with classloaders & reloading properly etc. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com