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 19 Next »


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. For most containers, Cargo automatically manages the container's classpath by adding the required container JARs to it. However, some containers support being embedded. This is the case of Jetty and the Jetty4xEmbeddedContainer implementation class simply starts the container in the running JVM. Thus you'll need to ensure to have the Jetty JAR + all the other related JARs required (jasper-compiler and jasper-runtime jars specifically).

In addition, for all non-embedded container implementations it is possible to add custom JARs to the container's execution classpath as shown below.

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:

  • No labels