Another mark in the calendar for the Arquillian team, 1.0.0.Alpha2 has just been released!

The Second fleet of the first wave has arrived!

(... Ooh boy, what a ride! Our transwarp speed engine went critical, had to eject the core and hustle a local merchant at a nearby tradestation for a new coil. A long story for some other time...)

Highlights of the release:

• @Run(AS_CLIENT) mode: Arquillian only controls the lifecycle of your @Deployment, the test case executes in your local JVM.   
  • Excellent for testing Remote EJBs, WebServices and web pages.

@RunWith(Arquillian.class)
@Run(AS_CLIENT)
public class LocalRunServletTestCase
{
   @Deployment
   public static WebArchive createDeployment() 
   {
      return ShrinkWrap.create("test.war", WebArchive.class)
            .addClass(TestServlet.class);
   }

   @Test
   public void shouldBeAbleToDeployWebArchive() throws Exception
   {
      String body = readAllAndClose(
            new URL("http://localhost:8080/test/Test").openStream());
      

      Assert.assertEquals(
            "Verify that the servlet was deployed and returns expected result",
            "hello",
            body);
   }
   ...
}

• Configuration: Set the address the container is bound to etc. using the arquillian.xml  
  • See the "Complete Container Reference" in the Reference Guide for more details.

<?xml version="1.0"?>
<arquillian xmlns="http://jboss.com/arquillian"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:jboss="urn:arq:org.jboss.arquillian.jbossas.local60">

   <jboss:container>
      <jbossHome>target/jboss-6.0.0.20100429-M3</jbossHome>
      <bindAddress>127.0.0.1</bindAddress>
      <httpPort>8080</httpPort>
   </jboss:container>     

</arquillian>

The containers you can depoy to in this release:

• JBoss AS 6.0 Embedded AS
• JBoss AS 6.0 Remote
• JBoss AS 6.0 with lifecycle(start/stop as part of the test run)
• JBoss AS 5.1 Remote
• JBoss AS 5.1 wth lifecycle(start/stop as part of the test run)
• JBoss Reloaded (MicroContainer + VirtualDeploymentFramework)   
  • Test your deployers and MC beans !
• Weld SE
• GlassFish Embedded 3.0
• Apache OpenEJB
• Apache OpenWebBeans

Arquillian no longer exposes the containers dependencies transitively, so you can control which container point release v. or logging framework the Arquillian integration should use. This might sound more complex at first, but see the "Complete Container Reference" in the Reference Guide for Maven examples on how to set this up for each container.

And what's open source without the community?!

Big thanks to the Arquillian and ShrinkWrap community for helping us with this release!

In alphabetical order: Dan Allen, German Escobar, Ken Gullaksen, Sten Aksel Heien, Alejandro Montenegro, Pete Muir, Jesper Pedersen, Andrew Lee Rubinger, Juergen Zimmermann.