Start a container. That task will:
Note: A container that's started with the
Start a container and wait for the user to press
Stop a container.
Stop and start again a container. If the container was not running before calling
Create the configuration for a local container, without starting it. Note that the
Start a container using the Cargo Daemon.
|Stop a container using the Cargo Daemon.|
Deploy a deployable to a running container.
Undeploy a deployable from a running container.
Undeploy and deploy again a deployable. If the deployable was not deployed before calling
Many wonder the difference between the
Here's a full example showing how to deploy a WAR, and expanded WAR and an EAR in an Orion 2.x container. Please note that the
log attribute are optional. The
property elements allow you to tune how the container is configured. Here we're telling it to start on port 8180 and to generate the maximum amount of logs in the container
<taskdef resource="cargo.tasks"> <classpath> <pathelement location="path/to/cargo-uberjar.jar"/> <pathelement location="path/to/cargo-ant-tasks.jar"/> </classpath> </taskdef> <cargo containerId="orion2x" home="c:/apps/orion-2.0.3" output="target/output.log" log="target/cargo.log" action="start"> <configuration> <property name="cargo.servlet.port" value="8180"/> <property name="cargo.logging" value="high"/> <deployable type="war" file="path/to/my/simple.war"/> <deployable type="war" file="path/to/my/expandedwar/simple"/> <deployable type="ear" file="path/to/my/simple.ear"/> </configuration> </cargo>
It is also possible to load the configuration properties from a file - simply use the
This example gives a walk through of how to get a Cargo Ant build to work with Tomcat 5.x .