Page Comparison

...

Top level configuration elements	Description	Default value
`<action>`	Action to execute. These can be: Container actions: `configure`, `start`, `restart`, `run` or `stop` Deployer actions: `deploy`, `undeploy` or `redeploy` Cargo Daemon actions: `daemon-start` or `daemon-stop`	No default
`<containerId>`	Id of the container to use. Valid values can be found in the description page for each container	No default
`<containerType>`	The container's type. Valid values are `installed`, `embedded` and `remote`	Default value is `installed`
`<home>`	Location where the container is installed. If specified in conjunction with the `<zipUrlInstaller>` element, it will override the home directory defined by the installer	No default If the user has not defined any `home` nor `<zipUrlInstaller>` element then the Ant task will automatically attempt to download the container using the URL used by its tests (see the Tested On section of each container).
`<zipUrlInstaller>`	Defines the location of a container distribution zip that will be downloaded and installed	No default If the user has not defined any `home` nor `<zipUrlInstaller>` element then the Ant task will automatically attempt to download the container using the URL used by its tests (see the Tested On section of each container).
`<timeout>`	The timeout after which Cargo reports an error if the container is not started or stopped	`120000` ms (2 minutes)
`<systemProperties>`	List of `<key>value</key>` pairs to be passed as System properties to the container when it is started. You can also use the `<systemPropertiesFile>` element to load system properties from a file.	No default
`<extraClasspath>`	Additional classpath entries for the classpath that will be used to start the containers.	No default
`<sharedClasspath>`	Classpath entries for the classpath that will be shared the applications deployed in a container. Shared application classpath deployment is only available for local containers which support shared Application Classpaths.	No default
`<log>`	Path to a file where Cargo logs are saved	Logs to the Ant console if no log file is specified
`<output>`	Path to a file where container logs are saved	Logs to the file specified by the `<log>` element or to the Ant console if no such file has been specified
`<append>`	If `true`, then the file specified by `<output>` will not be erased across different runs	`false`
`<configuration>`	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
`<daemon>`	Additional configuration that is used when deploying with the Cargo Daemon.	For more information, please read: Cargo Daemon.

...

<configuration> elements

Description

Mandatory?

Default value

<type>

Configuration's type. Valid values are standalone, existing and runtime

standalone

<home>

For standalone configuration this is the location where Cargo will create the configuration and for existing configuration this is where it is located

No default

<properties>

Values to use for various Configuration properties.

You can also use the <propertiesFile> element to load configuration properties from a file.

Default configuration properties

Note that these configuration properties can also be overriden using Java properties; for example:

Code Block
ant -Dcargo.servlet.port=8082

<deployables>

A list of deployables that are going to be deployed in the container when it is started or when deploy / undeploy is called.

No default

<fileConfigs>

List of Configuration files that are to be added to a local container's configuration. Each file is specified using a <fileConfig> element. Cargo token replacement is applied to the files and any existing file is overwritten.

No default

<files>

List of files that are to be added to a local container's configuration. Each file is specified using a <file> element.

No default

<xmlReplacements>

Values to use for various XML replacements.

No default

<users>

List of users to be created in container configuration.

No default

List of datasources to be created in container configuration.

No default

...

`<datasource>` elements	Description	Default value
`<jndiName>`	JNDI name where to find this DataSource.	No default
`<connectionType>`	Type of this DataSource ex. ", for example: `javax.sql.XADataSource`".	No default
`<transactionSupport>`	Transaction support of the datasource ex. "DataSource, for example: `XA_TRANSACTION`"	No default
`<driverClass>`	The class name of the Driver. Example: "driver, for example: `org.hsqldb.jdbcDriver`".	No default
`<url>`	DataSource connection URL.	No default
`<username>`	DataSource username.	No default
`<password>`	DataSource password.	Empty string
`<id>`	Id Identifier used in configuration files.	No default
`<connectionProperties>`	Extra properties passed to the DataSource.	No default

...

`<properties>` elements	Description	Mandatory?	Default value
`<cargo.daemon.url>`	URL to connect with the daemon.		No default
`<cargo.daemon.handleid>`	The handle id to register this container with.		No default
`<cargo.daemon.autostart>`	When set to `true`, the dameon will automatically restart the container if the daemon notices it is stopped.		`false`
`<cargo.daemon.username>`	Username used when authenticating against the daemon host		`admin`
`<cargo.daemon.password>`	Password used when authenticating against the daemon host	`""` (empty String)	Empty string

Versions Compared

Old Version 9

New Version Current

Key