Page History

...

Documentation	Reference	Description
guice:run	guice:run	Boots up Camel in a new JVM the context of a separately initiated Java thread using the Guice configuration in the jndi.properties file on the classpath and runs your routing rules
guice:embedded	guice:embedded	Boots up Camel in the same JVM as Maven using the Guice configuration at jndi.properties on the classpath and runs your routing rules
guice:dot	guice:dot	Generates DOT files and then HTML, PNG, SVG files for your EIP routing rules with integration into Maven Reports

...

Code Block

lang	xml

<plugin>
  <groupId>org.apache.camel</groupId>
  <artifactId>guice-maven-pluginplugin</artifactId>
</plugin>

You can also specify what Main class to use when running the plugin. By default this is org.apache.camel.guice.Main.

Code Block

lang	xml

<plugin>
  <groupId>org.apache.camel</groupId>
  <artifactId>guice-maven-pluginplugin</artifactId>
  <!-- optional, default value: org.apache.camel.guice.Main -->
  <configuration>
    <mainClass>mypackage.boot.camel.CamelStartup</mainClass>
  </configuration>
</plugin>

Making use of an optional JNDI properties file

Available as of Camel 2.13.0

Optionally if the name of your JNDI properties file is something else other than the default jndi.properties or if it's not on the default classpath, then you can make use of the jndiProperties option as shown below:

Code Block

lang	xml


<plugin>
  <groupId>org.apache.camel</groupId>
  <artifactId>guice-maven-plugin</artifactId>
  <configuration>
    <jndiProperties>/path/to/my/jndi/properties/my-guice-jndi.properties</jndiProperties>
  </configuration>
</plugin>

...

Code Block

lang	xml

<project>
  ...
  <reporting>
    <plugins>
      <plugin>
        <groupId>org.apache.camel</groupId>
        <artifactId>guice-maven-pluginplugin</artifactId>
      </plugin>
    </plugins>
  </reporting>  
</project>

...

Child pages

Versions Compared

Old Version 7

New Version Current

Key

Making use of an optional JNDI properties file