There are a few different approaches to configuring components and endpoints.
Which allows you to configure a component using some name (activemq in the above example), then you can refer to the component using activemq:[queue:|topic:]destinationName. This works by the SpringCamelContext lazily fetching components from the spring context for the scheme name you use for Endpoint URIs
Another approach is to use the URI syntax. The URI syntax supports the query notation. So for example with the Mail component you can configure the password property via the URI
Available as of Camel 2.0
When configuring endpoints using URI syntax you can now refer to beans in the Registry using the # notation.
Will lookup a bean with the id mySpecialFileSorter in the Registry.
Available as of Camel 2.3
When defining routes in Camel using Xml Configuration you may want to define some routes in other XML files. For example you may have many routes and it may help to maintain the application if some of the routes are in separate XML files. You may also want to store common and reusable routes in other XML files, which you can simply import when needed.
In Camel 2.3 it is now possible to define routes outside <camelContext/> which you do in a new <routeContext/> tag.
For example we could have a file named myCoolRoutes.xml which contains a couple of routes as shown:
Then in your XML file which contains the CamelContext you can use Spring to import the myCoolRoute.xml file.
Also notice that you can mix and match, having routes inside CamelContext and also externalized in RouteContext.
You can have as many <routeContextRef/> as you like.
You might first want to read Writing Components for a background in how to implement a new component.
You can then register your component explicitly via
However you can use the auto-discovery feature of Camel where by Camel will automatically add a Component when an endpoint URI is used. To do this you would create a file called
(you can add other property configurations in there too if you like)
Then if you refer to an endpoint as foo://somethingOrOther Camel will auto-discover your component and register it.
The FooComponent can then be auto-injected with resources using the Injector, such as to support Spring based auto-wiring, or to support @Resource (EJB3 style) injection or Guice style @Inject injection.
You can configure a component via Spring using the following mechanism...
Which allows you to configure a component using some name (activemq in the above example), then you can refer to the component using activemq:[queue:|topic:]destinationName.
If you want to add explicit Spring 2.x XML objects to your XML then you could use the xbean-spring which tries to automate most of the XML binding work for you; or you could look in camel-spring at CamelNamespaceHandler you'll see how we handle the Spring XML stuff (warning its kinda hairy code to look at . If you wanted <fooComponent> to be a standard part of the core Camel schema then you'd hack that file to add your component & conftribute a patch to the camel XSD. Otherwise you could write your own namespace & schema if you prefer.