Codehaus Cargo - JBoss 7.2.x

Codehaus Cargo > Containers > JBoss 7.2.x

With the opening of the JBoss EAP to the public and the split between JBoss and WildFly, the below naming correspondence should be used with JBoss EAP containers:

What Cargo calls JBoss 6.x is what JBoss refers to as JBoss Application Server version 6; i.e. the version released in December 2010
What Cargo calls JBoss 6.1.x is what JBoss refers to as JBoss Application Server version 6.1; i.e. the version released in August 2011
What Cargo calls JBoss 7.1.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.0; i.e. the build from JBoss Application Server (AS) version 7.1 released in February 2012
What Cargo calls JBoss 7.2.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.1; i.e. the build from JBoss Application Server (AS) version 7.2 released in May 2013
What Cargo calls JBoss 7.3.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.2; i.e. the build from JBoss Application Server (AS) version 7.3 released in October 2013
What Cargo calls JBoss 7.4.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.3; i.e. the build from JBoss Application Server (AS) version 7.4 released in June 2014
What Cargo calls JBoss 7.5.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.4; i.e. the build from JBoss Application Server (AS) version 7.5 released in October 2015
The WildFly 10.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.0; i.e. the version released in May 2016
The WildFly 11.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.1; i.e. the version released in December 2017
The WildFly 14.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.2; i.e. the version released in January 2019
The WildFly 18.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.3; i.e. the version released in March 2020
The WildFly 23.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.4; i.e. the version released in July 2021
The WildFly 28.x container can be used with the JBoss Enterprise Application Platform (EAP) version 8.0; i.e. the version released in February 2024

Container Features

Feature name	Java API	Ant tasks	Maven 3 plugin	Comment
Container Instantiation	`ContainerFactory.createContainer("jboss72x"...)`	`<cargo containerId="jboss72x".../>`	`<containerId>jboss72x</containerId>`
Local Container
Container Classpath				Read more on JBoss 7.x onwards and WildFly container classpath
Container Start
Container Stop
Container Timeout
Embedded Container
Installed Container	`o.c.c.c.jboss.JBoss72xInstalledLocalContainer`
Passing system properties
Installer
Remote Container	`o.c.c.c.jboss.JBoss72xRemoteContainer`

Configuration Features

Feature name	Java API	Ant tasks	Maven 3 plugin	Comment
Standalone Local Configuration for installed container	`o.c.c.c.jboss.JBoss72xStandaloneLocalConfiguration`
Standalone Local Configuration for embedded container
Existing Local Configuration for installed container	`o.c.c.c.jboss.JBoss72xExistingLocalConfiguration`
Existing Local Configuration for embedded container
Runtime Configuration	`o.c.c.c.jboss.JBoss7xRuntimeConfiguration`
Static deployment of WAR
Static deployment of expanded WAR
Static deployment of EJB
Static deployment of EAR
Static deployment of RAR
Static deployment of (JBoss) HAR
Static deployment of (JBoss) SAR
Static deployment of (JBoss) AOP
Static deployment of files
Static deployment of OSGi Bundles

Deployer Features

Feature name	Java API	Ant tasks	Maven 3 plugin	Comment
Installed Deployer	`o.c.c.c.jboss.JBoss7xInstalledLocalDeployer`
Embedded Deployer
Remote Deployer	`o.c.c.c.jboss.JBoss7xRemoteDeployer`

Other Features

Feature name	Java API	Ant tasks	Maven 3 plugin	Comment
Debugging

Supported Configuration properties

The tables below list both the general configuration properties as well as the container-specific ones.

Standalone Local Configuration Properties

For installed container o.c.c.c.jboss.JBoss72xInstalledLocalContainer

Property name	Java Property	Default value
cargo.hostname	GeneralPropertySet.HOSTNAME	`localhost`
cargo.java.home	GeneralPropertySet.JAVA_HOME	JAVA_HOME version 6 or newer Due to incompatibilities with its OSGi environment, JBoss 7.2.x doesn't run on Java 8 and above
cargo.jboss.ajp.port	JBossPropertySet.JBOSS_AJP_PORT	`8009`
cargo.jboss.configuration	JBossPropertySet.CONFIGURATION	`standalone`
cargo.jboss.deployer.keepOriginalWarFilename	JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME	`false`
cargo.jboss.deployment.dir	JBossPropertySet.ALTERNATIVE_DEPLOYMENT_DIR	N/A
cargo.jboss.https.port	JBossPropertySet.JBOSS_HTTPS_PORT	`8443`
cargo.jboss.management-http.port	JBossPropertySet.JBOSS_MANAGEMENT_HTTP_PORT	`9990`
cargo.jboss.management-https.port	JBossPropertySet.JBOSS_MANAGEMENT_HTTPS_PORT	`9993`
cargo.jboss.management-native.port	JBossPropertySet.JBOSS_MANAGEMENT_NATIVE_PORT	`9999`
cargo.jboss.modules.dir	JBossPropertySet.ALTERNATIVE_MODULES_DIR	`modules`
cargo.jboss.remoting.transport.port	JBossPropertySet.JBOSS_REMOTING_TRANSPORT_PORT	`4447`
cargo.jboss.script.cli.online	JBossPropertySet.CLI_ONLINE_SCRIPT	N/A
cargo.jvmargs	GeneralPropertySet.JVMARGS	N/A
cargo.logging	GeneralPropertySet.LOGGING	`medium`
cargo.port.offset	GeneralPropertySet.PORT_OFFSET	`0`
cargo.process.spawn	GeneralPropertySet.SPAWN_PROCESS	`false`
cargo.protocol	GeneralPropertySet.PROTOCOL	`http`
cargo.remote.password	RemotePropertySet.PASSWORD	N/A
cargo.remote.username	RemotePropertySet.USERNAME	N/A
cargo.runtime.args	GeneralPropertySet.RUNTIME_ARGS	N/A
cargo.servlet.port	ServletPropertySet.PORT	`8080`
cargo.servlet.users	ServletPropertySet.USERS	N/A
cargo.standalone.ignoreNonExistingProperties	GeneralPropertySet.IGNORE_NON_EXISTING_PROPERTIES	N/A
cargo.start.jvmargs	GeneralPropertySet.START_JVMARGS	N/A

Datasource and Resource configuration

In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.

For more details, please read: DataSource and Resource Support.

Existing Local Configuration Properties

For installed container o.c.c.c.jboss.JBoss72xInstalledLocalContainer

Property name	Java Property	Default value
cargo.hostname	GeneralPropertySet.HOSTNAME	`localhost`
cargo.java.home	GeneralPropertySet.JAVA_HOME	JAVA_HOME version 6 or newer Due to incompatibilities with its OSGi environment, JBoss 7.2.x doesn't run on Java 8 and above
cargo.jboss.ajp.port	JBossPropertySet.JBOSS_AJP_PORT	N/A
cargo.jboss.configuration	JBossPropertySet.CONFIGURATION	`standalone`
cargo.jboss.deployer.keepOriginalWarFilename	JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME	`false`
cargo.jboss.deployment.dir	JBossPropertySet.ALTERNATIVE_DEPLOYMENT_DIR	N/A
cargo.jboss.https.port	JBossPropertySet.JBOSS_HTTPS_PORT	N/A
cargo.jboss.management-http.port	JBossPropertySet.JBOSS_MANAGEMENT_HTTP_PORT	N/A
cargo.jboss.management-https.port	JBossPropertySet.JBOSS_MANAGEMENT_HTTPS_PORT	N/A
cargo.jboss.management-native.port	JBossPropertySet.JBOSS_MANAGEMENT_NATIVE_PORT	`9999`
cargo.jboss.modules.dir	JBossPropertySet.ALTERNATIVE_MODULES_DIR	`modules`
cargo.jboss.remoting.transport.port	JBossPropertySet.JBOSS_REMOTING_TRANSPORT_PORT	N/A
cargo.jboss.script.cli.online	JBossPropertySet.CLI_ONLINE_SCRIPT	N/A
cargo.jvmargs	GeneralPropertySet.JVMARGS	N/A
cargo.port.offset	GeneralPropertySet.PORT_OFFSET	`0`
cargo.process.spawn	GeneralPropertySet.SPAWN_PROCESS	`false`
cargo.protocol	GeneralPropertySet.PROTOCOL	`http`
cargo.remote.password	RemotePropertySet.PASSWORD	N/A
cargo.remote.username	RemotePropertySet.USERNAME	N/A
cargo.runtime.args	GeneralPropertySet.RUNTIME_ARGS	N/A
cargo.servlet.port	ServletPropertySet.PORT	`8080`
cargo.servlet.users	ServletPropertySet.USERS	N/A
cargo.start.jvmargs	GeneralPropertySet.START_JVMARGS	N/A

Datasource and Resource configuration

In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.

For more details, please read: DataSource and Resource Support.

Runtime Configuration Properties

Before using the JBoss remote deployer, please read: JBoss Remote Deployer

For remote container o.c.c.c.jboss.JBoss72xRemoteContainer

Property name	Java Property	Default value
cargo.hostname	GeneralPropertySet.HOSTNAME	`localhost`
cargo.jboss.clustered	JBossPropertySet.CLUSTERED	N/A
cargo.jboss.configuration	JBossPropertySet.CONFIGURATION	N/A
cargo.jboss.deployer.keepOriginalWarFilename	JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME	`false`
cargo.jboss.management-http.port	JBossPropertySet.JBOSS_MANAGEMENT_HTTP_PORT	N/A
cargo.jboss.management-https.port	JBossPropertySet.JBOSS_MANAGEMENT_HTTPS_PORT	N/A
cargo.jboss.management-native.port	JBossPropertySet.JBOSS_MANAGEMENT_NATIVE_PORT	`9999`
cargo.jboss.profile	JBossPropertySet.PROFILE	N/A
cargo.remote.password	RemotePropertySet.PASSWORD	N/A
cargo.remote.uri	RemotePropertySet.URI	N/A
cargo.remote.username	RemotePropertySet.USERNAME	N/A

Click here to read our privacy and cookie policy

Quick Links

Containers

Independent extensions

Development

Container Features

Configuration Features

Deployer Features

Other Features

Supported Configuration properties

Standalone Local Configuration Properties

For installed container o.c.c.c.jboss.JBoss72xInstalledLocalContainer

Existing Local Configuration Properties

For installed container o.c.c.c.jboss.JBoss72xInstalledLocalContainer

Runtime Configuration Properties

For remote container o.c.c.c.jboss.JBoss72xRemoteContainer