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

Mission

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

Status

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

Version

Status

Comments

0.1

(tick)

Released on 11/09/04

0.2

(tick)

Released on 03/10/04

0.3

(tick)

Released on 30/10/04

0.4

(tick)

Released on 26/11/04

0.5

(tick)

Released on 30/04/05

0.6

(tick)

Released on 21/07/05

0.7

(error)

Sometime in November 2005

1.0

(error)

End of year 2005?


Documentation for Cargo version in development

Icon

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

Architecture


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 Deployable before the Container is started.
  • You can use a Deployer to deploy Deployable dynamically (i.e. after the Container is started).
  • Deployables are archives to be deployed in the Container. They are WAR, EAR, etc.

Feature list

Some top-level features (the full feature list can be found here):

Container support

The pages for Codehaus Cargo have moved.

Click here to go to the new Codehaus Cargo page for Containers

Quick Start

The pages for Codehaus Cargo have moved.

Click here to go to the new Codehaus Cargo page for Quick start

  • No labels