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 4226E10CC7 for ; Wed, 12 Feb 2014 12:16:02 +0000 (UTC) Received: (qmail 48685 invoked by uid 500); 12 Feb 2014 12:16:01 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 47928 invoked by uid 500); 12 Feb 2014 12:15:59 -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 47916 invoked by uid 99); 12 Feb 2014 12:15:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 12:15:58 +0000 X-ASF-Spam-Status: No, hits=-3.7 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ecaruana@cisco.com designates 173.37.86.79 as permitted sender) Received: from [173.37.86.79] (HELO rcdn-iport-8.cisco.com) (173.37.86.79) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 12:15:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1617; q=dns/txt; s=iport; t=1392207351; x=1393416951; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=VCbJ9NEn2m+Vl+GNU2KDyAvWubtAY6ankujcc8UuvGo=; b=EyVrZGOfZJslhQddgpECU+ygRalCv2RD5br2MZtKQt5BPyPxMvnmB9Y6 FxvlaFFb349WKSiWV2B1uw0BAYX7eFv3BUpspzeqjzyR+33QMX2QdGe8a FBeEHjHzEd1PAS2SpVcnXDoXQdOGWaMHRaq7KCyOnKpcoVvaMQQeyM8uP s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkIFAAtl+1KtJV2Z/2dsb2JhbABagww4V6orlH2BERZ0giUBAQEEOjQXBAIBCBEEAQELFAkHMhMBCQgCBBMIh2kDEQ3ALReIJBeMX4FpMwUGgx6BFASWRIMYiyyFQ4Mtgio X-IronPort-AV: E=Sophos;i="4.95,832,1384300800"; d="scan'208";a="303540988" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 12 Feb 2014 12:15:29 +0000 Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1CCFTRR009985 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 12 Feb 2014 12:15:29 GMT Received: from xmb-rcd-x07.cisco.com ([169.254.7.211]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Wed, 12 Feb 2014 06:15:29 -0600 From: "Elvio Caruana (ecaruana)" To: "users@camel.apache.org" Subject: RE: Create Camel routes as plugins - loose coupled from legacy routes Thread-Topic: Create Camel routes as plugins - loose coupled from legacy routes Thread-Index: AQHPJ1szGE+eRVjnDEaJNSkMutrjLJqxg2lQ Date: Wed, 12 Feb 2014 12:15:28 +0000 Message-ID: References: <1392140186719-5747125.post@n5.nabble.com> In-Reply-To: <1392140186719-5747125.post@n5.nabble.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.38.178.65] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org +camel-users (I think this question is more appropriate for the users mailing list.) But to answer your question, the recipient list EIP will allow you to 'dyna= mically' set (or change) the endpoint using an expression (e.g. value in he= ader, or from a constant configuration value). Similarly, the routing slip EIP will allow you to define the full sequence = at run-time. http://camel.apache.org/routing-slip.html Elvio -----Original Message----- From: shmennen [mailto:shmennen@yahoo.com]=20 Sent: 11 February 2014 17:36 To: dev@camel.apache.org Subject: Create Camel routes as plugins - loose coupled from legacy routes Hello All, I want to use Camel in achieving the following scenario: - suppose we have a bunch of legacy base routes (cannot change them) - apart that I want to create new routes (like a plugin or extension routes= ), loose coupled with legacy base routes. These routes should be easily rep= laced with other custom route implementations Example: suppose we have legacy routes A - B - C I want to create routes D1 and E1 to be loose coupled with A, = B and C and to have the possibility to replace them any time (by another D2= and E2 routes).=20 Routes A, B and C to be included in one jar, routes D and E in= another jar. =20 What is the best design of doing that ? Thanks, Shmennen -- View this message in context: http://camel.465427.n5.nabble.com/Create-Came= l-routes-as-plugins-loose-coupled-from-legacy-routes-tp5747125.html Sent from the Camel Development mailing list archive at Nabble.com.