Page History

...

META-INF/spring/*.xml

If you want to boot up your Camel routes a little faster, you could try the camel:embedded instead.

Running OSGi Blueprint

From Camel 2.10 onwards the camel:run plugin also supports running Blueprint application, and by default it scans for OSGi blueprint files in

OSGI-INF/blueprint/*.xml

You would need to configure the camel:run plugin to use blueprint, by setting useBlueprint to true as shown below

      <plugin>
        <groupId>org.apache.camel</groupId>
        <artifactId>camel-maven-plugin</artifactId>
        <configuration>
          <useBlueprint>true</useBlueprint>
        </configuration>
      </plugin>    

This allows you to boot up any Spring Blueprint services you wish; whether they are Camel related or any other Spring POJOs or Blueprint.If you want to boot up your Camel routes a little faster, you could try the camel:embedded instead

You can use the applicationContextUri configuration to specify an explicit blueprint XML file, such as:

      <plugin>
        <groupId>org.apache.camel</groupId>
        <artifactId>camel-maven-plugin</artifactId>
        <configuration>
          <useBlueprint>true</useBlueprint>
          <applicationContextUri>myBlueprint.xml</applicationContextUri>
        </configuration>
      </plugin>    

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.

About DOT generation

camel:run will by default try to run dot generation to generate Visualisation diagrams.
This feature could in some rare cases cause the application to hang, so its by default disabled in Camel 1.6.1 or newer.

...