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


Cargo is a thin wrapper around existing containers (e.g. J2EE containers). It provides different APIs to easily manipulate containers.

Cargo provides the following APIs:

  • A Java to start/stop/configure Java Containers and deploy modules into them. We also offer Ant tasks, Maven 1, Maven 2, Intellij IDEA and Netbeans plugins.
  • A Java API to parse/create J2EE Modules


Version status (click in the status column to get release notes):






Released on 11/09/04



Released on 03/10/04



Released on 30/10/04



Released on 26/11/04



Released on 30/04/05



Released on 21/07/05



Sometime in November 2005



End of year 2005?

Documentation for Cargo version in development


The documentation below is for Cargo 0.7 which is the version that we are currently developing (not released yet). The documentation for Cargo 0.6 (latest released version) is available here


Cargo offers differents ways of using it at different levels:

  • Module Java API: A Java API to parse/create J2EE Modules (WAR, EAR, etc)
  • Container Java API: A Java API to start/stop/configure Java Containers and deploy modules into them.
  • Generic Java API: A Java API that sits on top of the Container API but allows writing generic code that works with any container. It consists mostly in a set of Factory classes to instantiate Container API objects by name.
  • Build plugins
  • IDE plugins
    • Netbeans plugin
    • IntelliJ IDEA

The main Container API objects are:

  • The Container is the top level interface wrapping a real physical container. Cargo supports local and remote containers. A Container is composed of a Configuration.
  • A Configuration tells Cargo how the container is to be configured (whether it should create a standalone setup, whether it should be based on an existing configuration, etc). A Configuration can be configured to install Deployables before the Container is started.
  • You can use a Deployer to deploy Deployables dynamically (i.e. after the Container is started).
  • Deployables are archives to be deployed in the Container. They are WAR, EAR, etc.

Feature list

Container support


Quick Start

The following examples demonstrate how to configure Resin 3.0.15 to start in target/resin3x and deploy a WAR located in path/to/simple.war. The default port is 8080. Please note that the container.start() and container.stop() methods wait until the container is fully started and fully stopped before continuing. Thus, for any action you are executing after, you are assured the container is completely operational.

Static deployment

Static deployment means that the Deployabe is deployed before the container is started. Here's an example using the strongly type Java API:

Here's the same example using the generic untyped API:

Dynamic deployment

Dynamic deployment means that the Deployable is deployed after the container is started.

  • No labels