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

Definition

How to configure the classpath of the application without changing the container's own classpath
Icon

This feature is only available for local containers

Icon

This feature is not available on all containers! Currently, the only containers that support shared classpaths are:

  • JBoss 5.x to 6.1.x (inclusive)
  • JBoss 7.x and 7.1.x; by modifying your application's MANIFEST.MF file (read more on the how to put an external file in the classpath article from the JBoss website)
  • Jetty 6.x and onwards
  • All Tomcat containers

On other containers, please change the container classpath instead.

Explanation

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 application being executed on a container.

Some environments may require you to add some libraries to your application, without exposing them to the server itself. This concept is called a Shared Classpath.

Example using the Java API

Starting a WAR on Tomcat 6.x with some additional classpath entries:

Example using the Ant API

Starting a WAR on Tomcat 6.x with some additional classpath entries:

Example using the Maven Plugin

Configuring a Tomcat6 container with a com.foo bar-api-1.0.jar dependency provided using the shared classpath:

  • No labels