Java Reference
In-Depth Information
After that, since our Arquillian test uses a protocol to communicate with the server
application, we will need to add the
org.jboss.arquillian.protocol
depend-
ency (named so as it's compatible with Servlet 2.5/3.0 specifications):
<dependency>
<groupId>org.jboss.arquillian.protocol</groupId>
<artifactId>arquillian-protocol-servlet</artifactId>
<scope>test</scope>
</dependency>
The last dependency that we will add is the
weld
container dependency; this will be
needed as we will test some advanced CDI techniques such as ConversationScoped
communication:
<dependency>
<groupId>org.jboss.weld</groupId>
<artifactId>weld-core-test-arquillian</artifactId>
<version>1.1.9.Final</version>
</dependency>
After getting done with the dependencies, we will now include two profiles into our
configuration. A profile can basically be used to create different target environments
for our goals; in our case, we will create two profiles:
• The first profile is named
arq-jbossas-managed
; it will start a new
JBoss AS instance and execute the test, shutting it down when done:
<profile>
<id>arq-jbossas-managed</id>
<dependencies>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-arquillian-container-managed</artifactId>
