camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fruxo <fru...@gmail.com>
Subject Camel Context modularisation
Date Wed, 27 Mar 2013 22:29:25 GMT
Hi all,
I am new to Camel and, after a few days of investigations, it does not seem
to me that it is currently possible to achieve the same level of
Camel-context modularisation obtainable with Spring-contexts, am I right?

The use-case I am thinking of might be simply expressed as the need to:
1. have the Camel-context defined in one file
2. have the different routes defined one in an individual file
3. the single Camel-context defined at (1) imports the contexts defined at
(2) possibly via some simple name that supports wild-cards i.e.

The main value is that the artefacts would look much cleaner than having
everything in one single place, not to mention that it would also be
possible to dynamically add new routes to the Camel-context by loading at
runtime other XMLs (the ones defined as per (2)).

So, in conclusion:
- is this currently possible? How?
- if not, is there any suitable extension point in the Camel API that would
allow me to reach my goal?

Thanks in advance,
Francesco
 



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Context-modularisation-tp5729984.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message