Containers represent what your application will run on. This is the code that represents what you would typically run on top of the application server. The deployments though are what represent your code as standard Java Archives – JAR, WAR, EAR, RAR—that can be deployed to an application server to run code.
At the start of this, I want to remind you to consult with the Arquillian Reference Guide for the latest container setup. The list of containers can be found at https://docs.jboss.org/author/display/ARQ/Container+adapters.
This section is meant to be a brief crash course in using ShrinkWrap to create archives. The ShrinkWrap API is designed via Factory and Builder patterns. There is a utility class – ShrinkWrap
– that acts as the entrance for the factory of archives. Calling ShrinkWrap.create(JavaArchive.class);
will generate a new Java Archive (representing a JAR file).
Arquillian uses a static method defined in your test case to create the archive...