Difference between standalone.xml and standalone-full.xml

Question

What is the Difference between standalone.xml and standalone-full.xml. In what scenarios we use standalone-full.xml

Answer 1

• standalone.xml: Support of Java EE Web-Profile plus some extensions like RESTFul Web Services and support for EJB3 remote invocations
• standalone-full.xml: Support of Java EE Full-Profile and all server capabilities without clustering
• standalone-ha.xml: Default profile with clustering capabilities
• standalone-full-ha.xml: Full profile with clustering capabilities

Answer taken from: The Differences Between JBoss EAP 5 and EAP 6

Answer 2

From RHELSM (https://access.redhat.com/solutions/1136103)

1. standalone.xml: This is the default configuration file for a standalone server. It contains all information about the standalone server, including subsystems, networking, deployments, socket bindings, and other configurable details. This configuration is used automatically when you start your standalone server.

2. standalone-full.xml: This is an example configuration for a standalone server. It includes support for every possible subsystem except for those required for high availability.

3. standalone-ha.xml: This example configuration file enables all of the default subsystems and adds the mod_cluster and JGroups subsystems for a standalone server, so that it can participate in a high-availability or load-balancing cluster.

4. standalone-full-ha.xml: This is an example configuration for a standalone server. It includes support for every possible subsystem, including those required for high availability.

The server configuration for Messaging is contained in the $EAP_HOME/standalone/configuration/standalone-full.xml or $EAP_HOME/standalone/configuration/standalone-full-ha.xml file for standalone servers. The element in the server configuration file contains all JMS configuration.

It says, full config also include sub config:

• standalone-full.xml has standalone.xml
• standalone-full-ha.xml has standalone-ha.xml