...
Top level configuration elements | Description | Mandatory? | Default value |
|---|---|---|---|
Definition of a Configuration |
| Defaults to a standalone configuration if the container is of type local and a runtime one if it's of type remote | |
Definition of a Container |
| Defaults to a Jetty 7.x installed container if not specified | |
Definition of a Deployer |
| Defaults to a deployer matching the container's type if none is specified (installed local deployer for an installed container, remote deployer for a remote container and embedded local deployer for an embedded container) | |
A list of deployables that are going to be deployed in the container when it is started or when |
| If the project's packaging is | |
A list of properties that are used when deploying with the Cargo Daemon. |
| Cargo Daemon properties. For more information, please read: Cargo Daemon. | |
| Set this to |
| Defaults to |
| Decides if Cargo should wait after the container is started or not. If using Cargo for integration tests, set it to |
|
|
...
| Info | ||
|---|---|---|
| ||
Many containers have their specific files for redefining context roots (Tomcat has context.xml, JBoss has jboss-web.xml, etc.). If your WAR has such a file, the server will most probably use the context root defined in that file instead of the one you specify using the CARGO deployer. |
| Anchor | ||
|---|---|---|
|
| Description | Mandatory? | Default value |
|---|---|---|---|
| URL to connect with the daemon. |
| No default |
| The handle id to register this container with. |
| No default |
| Tells the daemon to autostart this container if it is stopped. |
| false |
...