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 CE66C44D1 for ; Wed, 25 May 2011 16:32:36 +0000 (UTC) Received: (qmail 27658 invoked by uid 500); 25 May 2011 16:32:36 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 27629 invoked by uid 500); 25 May 2011 16:32:36 -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 27621 invoked by uid 99); 25 May 2011 16:32:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2011 16:32:36 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [80.237.132.225] (HELO wp218.webpack.hosteurope.de) (80.237.132.225) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2011 16:32:28 +0000 Received: from p5de9401a.dip0.t-ipconnect.de ([93.233.64.26] helo=[172.17.16.53]); authenticated by wp218.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1QPH0C-0001tu-76; Wed, 25 May 2011 18:32:08 +0200 Message-ID: <4DDD2F07.5090202@catify.com> Date: Wed, 25 May 2011 18:32:07 +0200 From: Claus Straube User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: Camel Activator OSGI References: <1306250036263-4422370.post@n5.nabble.com> <4DDCA11E.2050902@gmail.com> <1306328757555-4425200.post@n5.nabble.com> <1306338255812-4425706.post@n5.nabble.com> In-Reply-To: <1306338255812-4425706.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;claus.straube@catify.com;1306341148;d7009492; X-Virus-Checked: Checked by ClamAV on apache.org Hi Jeff, I think you have to separate between the camel context and routes. If I understand your case correctly you want to load an externally defined route (as xml file) into your running camel context? So a simple solution would be to create a bundle with the camel context and one route that reads your route from file system, ftp or what ever. Then processing the route xml and giving the route to the camel context (see http://camel.apache.org/loading-routes-from-xml-files.html). Best regards - Claus On 25.05.2011 17:44, jguion wrote: > I am fairly new to OSGI and have never explicitly used the spring extender > but it looks like it is automatically installed if you use spring-dm. I can > take that approach and bundle up just my camel-context.xml and when I hot > deploy it, it will run the route correctly. I was trying to find a way to > just create a custom camelcontext file from our application instead of > having to create a whole bundle (jar). > It still seems strange I cannot use my own activator if I have one defined. > I think that if the camel-core bundle is installed and running in your > container, Karaf will try to use the camel activator and bypass any other > Activators, even for bundles that do not use camel and have no camel > dependencies. Would anyone be able to confirm this or know of a work around? > Thanks > > -- > View this message in context: http://camel.465427.n5.nabble.com/Camel-Activator-OSGI-tp4422370p4425706.html > Sent from the Camel - Users mailing list archive at Nabble.com. >