Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Current »


How to configure the executing container's classpath


This feature is only available for local containers


This topic is not about the classpath requirements to run Cargo (see the Installation page for this); it's about configuring the classpath for the executing container. You can therefore add custom JARs (code instrumentation, DataSource JARs, security-related libraries, etc.) to the container's execution classpath as shown below.

Note that some containers also support adding custom JARs to the applications' classpath only: see Application Classpath for details.

Example using the Java API

Starting Orion 1.x with Clover jar added to its classpath. For example if you have instrumented your source code with Clover you'll need to add the Clover jar to the classpath.

Example using the Ant API

Starting Orion 1.x with some additional classpath entries:

Example using the Maven 2 Plugin

See Starting and stopping a container - Adding jars to a container's classpath

  • No labels