This page has been automatically generated by Cargo's build. Do not edit it directly as it'll be overwritten next time it's generated again.
With the opening of the JBoss EAP to the public and the split between JBoss and WildFly, the below naming correspondance should be used with JBoss EAP containers:
- 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.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; 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
Container Features
Feature name | Java API | Ant tasks | Maven 2 / Maven 3 plugin | Comment |
---|---|---|---|---|
| | | ||
| ||||
|
Configuration Features
Feature name | Java API | Ant tasks | Maven 2 / Maven 3 plugin | Comment |
---|---|---|---|---|
| ||||
| ||||
| ||||
Deployer Features
Feature name | Java API | Ant tasks | Maven 2 / Maven 3 plugin | Comment |
---|---|---|---|---|
| ||||
|
Other Features
Feature name | Java API | Ant tasks | Maven 2 / Maven 3 plugin | Comment |
---|---|---|---|---|
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.JBoss6xInstalledLocalContainer
Property name | Java Property | Supported? | Default value | Javadoc |
---|---|---|---|---|
| ||||
JAVA_HOME version 6 or newer | ||||
| ||||
| ||||
| ||||
N/A | ||||
| ||||
| ||||
| ||||
| ||||
| ||||
N/A | ||||
N/A | ||||
N/A | ||||
| ||||
N/A | ||||
| ||||
| ||||
| ||||
N/A | ||||
| ||||
| ||||
| ||||
| ||||
N/A | ||||
N/A | ||||
| ||||
N/A | ||||
| ||||
N/A | ||||
N/A | ||||
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.
A side note on the JBoss ports:
- The
cargo.rmi.port
corresponds to thePort
parameter of thejboss:service=Naming
bean. - The
cargo.jboss.naming.port
corresponds to theRmiPort
parameter of thejboss:service=Naming
bean.
Existing Local Configuration Properties
For installed container o.c.c.c.jboss.JBoss6xInstalledLocalContainer
Property name | Java Property | Supported? | Default value | Javadoc |
---|---|---|---|---|
| ||||
JAVA_HOME version 6 or newer | ||||
| ||||
N/A | ||||
N/A | ||||
| ||||
| ||||
| ||||
N/A | ||||
N/A | ||||
| ||||
N/A | ||||
| ||||
N/A |
Runtime Configuration Properties
Before using the JBoss remote deployer, please read: JBoss Remote Deployer
For remote container o.c.c.c.jboss.JBoss6xRemoteContainer
Property name | Java Property | Supported? | Default value | Javadoc |
---|---|---|---|---|
| ||||
| ||||
| ||||
| ||||
N/A | ||||
N/A | ||||
N/A | ||||
|
Tested On
This container is automatically tested by the Continous Integration system every time there is a code change.
The server used for tests is downloaded from: https://repository.jboss.org/org/jboss/jbossas/jboss-as-distribution/6.0.0.Final/jboss-as-distribution-6.0.0.Final.zip