Arquillian.xml configuration file reference

by

Here is a table which summarizes the options which you can include into the arquillian.xml configuration file:

Property Default Description
jbossHome $JBOSS_HOME The JBoss configuration to start.
javaHome $JAVA_HOME The Java runtime to use to start the server.
modulePath $module.path The location of the module repository.
javaVmArguments -Xmx512m -XX:MaxPermSize=128m JVM arguments used to start the server.
startupTimeoutInSeconds 30 Time to wait before throwing Exception on server startup.
outputToConsole true Should the server startup console log be piped to the console
serverConfig standalone.xml Which server configuration file to startup with
managementAddress 127.0.0.1 The ip address of the running server instances manage interface
managementPort 9990 The management port for deployment
allowConnectingToRunningServer false If true, if a running AS is found on managementPort, it is used; if false, fails.

And here’s a sample configuration:

<arquillian xmlns="http://jboss.org/schema/arquillian"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://jboss.org/schema/arquillian
        http://jboss.org/schema/arquillian/arquillian_1_0.xsd">

	<!-- Force the use of the Servlet 3.0 protocol with all containers, as it 
		is the most mature -->
	<defaultProtocol type="Servlet 3.0" />

	<!-- Example configuration for a remote WildFly instance -->
	<container qualifier="jboss" default="true">
		<!-- By default, arquillian will use the JBOSS_HOME environment variable. 
			Alternatively, the configuration below can be uncommented. -->
		<configuration>
			<property name="jbossHome">/home/jboss/wildfly-10.1.0.Final</property>
			<property name="javaVmArguments">-Xmx512m -XX:MaxPermSize=256m -Djboss.modules.system.pkgs=com.sun.tools.attach,org.jboss.byteman -Xbootclasspath/a:/home/francesco/jdk1.8.0_60/lib/tools.jar</property>
			<property name="allowConnectingToRunningServer">true</property>
		</configuration>
	</container>

</arquillian>