This makes it very easy to spin up and test your routing rules without having to write a main(…) method; it also lets you create multiple jars to host different sets of routing rules and easily test them independently.
How this works is that the plugin will compile the source code in the maven project, then boot up a Spring ApplicationContext using the XML confiuration files on the classpath at
If you want to boot up your Camel routes a little faster, you could try the camel:embedded instead.
From Camel 2.10 onwards the camel:run plugin also supports running a Blueprint application, and by default it scans for OSGi blueprint files in
You would need to configure the camel:run plugin to use blueprint, by setting useBlueprint to true as shown below
This allows you to boot up any Blueprint services you wish - whether they are Camel-related, or any other Blueprint.
You can use the applicationContextUri configuration to specify an explicit blueprint XML file, such as:
The applicationContextUri will currently load the file from the classpath, so in the example above the myBlueprint.xml file must be in the root of the classpath.
From Camel 2.11 onwards the camel:run plugin also supports running a CDI application
You would need to configure the camel:run plugin to use CDI, by setting useCDI to true as shown below
This allows you to boot up any CDI services you wish - whether they are Camel-related, or any other CDI enabled services.
You should add the CDI container of your choice (e.g. Weld or OpenWebBeans) to the dependencies of the camel-maven-plugin such as in this example.
From the source of Camel you can run a CDI example via
camel:run will by default try to run dot generation to generate Visualisation diagrams.
To enable it you should configure the useDot parameter:
From Camel 2.10 onwards you can configure whether the classpath should be logged when camel:run executes. In older releases the classpath is always logged.