Spring Java Config
Spring started life using XML Config to wire beans together. However some folks don't like using XML and would rather use Java code which led to the creation of Guice along with the Spring JavaConfig project.
You can use either the XML or Java config approaches with Camel; its your choice really on which you prefer.
Using Spring Java Config
To use Spring Java Config in your Camel project the easiest thing to do is add the following to your pom.xml
This will then add the dependencies on the Spring JavaConfig library along with some helper classes for configuring Camel inside Spring.
Note that this library is totally optional; you could just wire Camel together yourself with Java Config.
The most common case of using JavaConfig with Camel would be to create configuration with defined list of routes to be used by router.
Starting from Camel 2.13.0 you can skip the routes() definition, and fall back to the RouteBuilder instances located in the Spring context.
Since Camel 2.11.0 you can use the
CamelSpringDelegatingTestContextLoader. This is the recommended way to test Java Config and Camel integration.
The following example using Java Config demonstrates how to test Java Config integration with Camel 2.10 and lower. Keep in mind that
JavaConfigContextLoader is deprecated and could be removed in the future versions of Camel on the behalf of the