camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Kripalani (JIRA)" <>
Subject [jira] [Created] (CAMEL-5858) Camel Context Inheritance
Date Mon, 10 Dec 2012 10:07:21 GMT
Raul Kripalani created CAMEL-5858:

             Summary: Camel Context Inheritance
                 Key: CAMEL-5858
             Project: Camel
          Issue Type: New Feature
          Components: camel-core
            Reporter: Raul Kripalani
            Assignee: Raul Kripalani

Camel is a great foundation for building SOA-based integration platforms. 

To improve governance and code manageability, one tends to define a number of common policies/items
to apply across all routes in the system, e.g. exception handlers, data format configurations,
property placeholder configurations, component configurations, etc.

If you use Spring, defining common component configs is possible by placing them in a separate
Spring App Context file and using Spring's <import /> directive, since components are
just standard beans.

However, for Camel-specific elements, there's no good solution, so you end up repeating yourself
a lot... Consider this for a DRY solution:

<camelContext id="parent.config" abstract="true">
    ... do something here...
    <json ... />
    <jaxb ... />
  <propertyPlaceholder id="properties" location="ref:myProperties"/>

A new Camel Context could "absorb" the config above like this:

<camelContext parentId="parent.config">
  ... specific configuration ...
  ... routes ...

This works nicely with OSGi because Camel Contexts are enlisted in the Service Registry, so
they can access and introspect each other. For other environments, we'll have to design something

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message