...
Notice: When you use <routeContext>
then they are separated, and cannot reuse existing <onException>
, <intercept>
, <dataFormats>
and similar cross cutting functionality defined in the <camelContext>
. In other words the <routeContext>
is currently isolated. This may change in Camel 3.x.
For example we could have a file named myCoolRoutes.xml
which contains a couple of routes as shown: Wiki Markup myCoolRoute.xml
file. And then inside <camelContext/>
you can refer to the <routeContext/>
by its id
as shown below: Wiki Markup CamelContext
and also externalized in RouteContext
.
You can have as many <routeContextRef/>
as you like.
...
...
The routes defined in <routeContext/>
can be reused by multiple <camelContext/>
. However its only the definition which is reused. At runtime each CamelContext
will create its own instance of the route based on the definition.