JBoss AS 7.0 - Remote - Arquillian Old

A DeployableContainer implementation that can connect and run against a remote(different JVM, different machine) running JBoss AS 7.0 instance.
This implementation has no lifecycle support, so it can not be started or stopped.

Container Injection Support Matrix

@EJB	@EJB (no-interface)	@Inject (CDI)	@Inject (MC)	@PersistenceContext @PersistenceUnit

The JBossAS7 container also support OSGi Bundle / Context injection in OSGi modules and Module Contexts/ServiceController when developing Modules (only when using the jmx-as7 protocol).

Configuration

Default Protocol: jmx-as7

Container Configuration Options

Name	Type	Default	Description
managementAddress	String	127.0.0.1	The ip address of the running server instances management interface
managementPort	int	9999	The management port for deployment

Example of Maven profile setup

<profile>
    <id>jbossas-remote-7</id>
    <dependencies>
        <dependency>
            <groupId>org.jboss.spec</groupId>
            <artifactId>jboss-javaee-6.0</artifactId>
            <version>1.0.0.Final</version>
            <type>pom</type>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.jboss.as</groupId>
            <artifactId>jboss-as-arquillian-container-remote</artifactId>
            <version>7.0.2.Final</version>
        </dependency>
    </dependencies>
</profile>

For JBoss AS 7.0.0.Final, you need to configure the jmx protocol used. Example:

<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://jboss.org/schema/arquillian"
	xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">

    <container qualifier="jboss7" default="true">
        <protocol type="jmx-as7">
            <property name="executionType">REMOTE</property>
        </protocol>
    </container>
</arquillian>

This has been fixed in JBoss AS 7.0.1.Final