+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 'dynamically' set (or change) the endpoint using an expression (e.g. value in header, 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:shmen...@yahoo.com] 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 replaced 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). Routes A, B and C to be included in one jar, routes D and E in another jar. What is the best design of doing that ? Thanks, Shmennen -- View this message in context: http://camel.465427.n5.nabble.com/Create-Camel-routes-as-plugins-loose-coupled-from-legacy-routes-tp5747125.html Sent from the Camel Development mailing list archive at Nabble.com.
