You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
Mission
Cargo provides a Java API to start/stop and configure Java containers
Possible use cases for Cargo:
- To start containers for integration and functional tests
- To start containers for applications that require a container to be started (Plugins for IDEs, etc)
Status
Version status (click in the status column to get release notes):
Version |
Status |
Comments |
|---|---|---|
|
Released on 11/09/04 |
|
|
Released on 03/10/04 |
|
|
Released on 30/10/04 |
|
|
Released on 26/11/04 |
|
0.5 |
|
Sometime in April 2005 would be good |
As glitches may happen even after a container is released for the first time, e.g. if a new feature is added to the framework, but not supported by all containers, we encourage you to report your success/failures in the Tested on section.
 | Documentation for Cargo version in development The documentation below is for Cargo 0.5 which is the version that we are currently developing (not released yet). The documentation for Cargo 0.4 (latest version) is available here |
Architecture
| There are no images attached to this page. |
- The Container is the top level interface wrapping a real physical container. It is composed of a Configuration. You can use a Deployer to deploy Deployables.
- 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)
- Deployables are archives to be deployed in the Container. They are WARs, EARs, etc.
Feature list
- Configuration — A Configuration specifies how the container is configured (logging, security, data sources, location where to put deployables, etc).
- Container — A top level interface wrapping a real physical container
- Debugging — Explain how to perform debugging when something doesn't work in Cargo
- Deployment — How to deploy components to a container
- Extensions — Extensions are additions to the Cargo core Java API such as build tool plugins, IDE plugins, etc
- Module API — API to manipulate J2EE archives, including vendor-specific deployment descriptors
Container support
Container |
Java API/version |
Ant API/version |
Maven API/version |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quick Start
The following piece of code demonstrates how to configure Resin 3.0.8 to start in target/resin3x and deploy a WAR located in src/testinput/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:
Dynamic deployment: