Version 18
    h2. Overview

    As development begins on the Seam 3 JMS Module, Aquillian has already made it very easy to verify the early functionality. This article explains how Arquillian has been used to demonstrate that injection of JMS resources and forwarding CDI events to JMS works correctly.


    h2. Injection Testing

    In order to test injection of JMS resources, those resources must be available. That means testing in the container, Arquillian's mantra!


    For now, all tests are set up using the Arquillian jboss-remote-60 profile, allowing us to test on a running instance of JBoss AS 6.0. Our initial tests use JUnit 4 and assume JBoss messaging is installed as the JMS provider.  While temporary topics can be created programatically, I wanted to additionally test the deployment of JBoss Messaging destinations through Arquillian. JBoss Messaging allows deployment descriptors for destinations to be bundled with deployments, allowing us to set up this test case for JMS resource injection entirely within Arquillian.


    In order to test simple destination injection we need to set up the ShrinkWrap deployment archive to include the JMS portable extension, required classes, and the configuration for the topic destination:


    public class JmsResourceInjectionTest {
       public static Archive<?> createTestDeployment()
          return Archives.create("test.jar", JavaArchive.class)
             .addPackages(false, Seam3JmsExtension.class.getPackage(), SimpleInjectionTest.class.getPackage())
             .addManifestResource(new ByteArrayAsset(new byte[0]), ArchivePaths.create("beans.xml"))
             // Register the portable extension
             .addServiceProvider(Extension.class, Seam3JmsExtension.class)
             // Include JBoss Messaging topic configuration


    Here's the topic destination configuration, topic_T-service.xml:


    {code:xml}<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
       <mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
          <attribute name="JNDIName">jms/T</attribute>
          <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>


    With the deployment set up to register our portable extension and resources, we can now test injection of a topic directly into the test class.


    {code:java}@Inject Topic t;

    public void simpleTopicInjection()
        assertEquals("T", t.getTopicName());


    The injection point is satisfied by a Topic producer method, which takes the name of the field, captializes it, appends it to the string "/jms/" and looks up the name (in this case /jms/T) in the JNDI InitialContext.


    h2. Bridged Events

    Where Arquillian has really begun to show its potential is when testing CDI events bridged to JMS. To provide some background, the Seam 3 JMS module will provide support for declaratively forwarding events over JMS.  While there are a few components involved in making this work, let's take a look at one of the test cases that verifies the events are being forwarded to their proper destination.


    We must be able to identify when messages are sent over JMS.  To do this we use a MessageConsumer and a simple test event.


    {code:java}@Inject Connection c;
    @Inject Session s;
    @Inject @Events Topic t;
    @Inject Seam3JmsExtension jmsExt;
    @Inject Event<String> event;{code}


    The test case requires that we register our event type to be forwarded over JMS, create a MessageConsumer to consume events from the intended destination, fire the event and check if we received it over the destination:


    public void forwardEvent() throws Exception
       String expected = "test";
       jmsExt.register(String.class, t);
       MessageConsumer mc = s.createConsumer(t);
       Message m = mc.receive();
       assertTrue(m instanceof ObjectMessage);
       assertEquals(expected, ((ObjectMessage) m).getObject());


    You can read more about CDI events in the Weld reference documentation.


    h2. What's Next

    We've taken a look into how Arquillian is making it possible to rapidly test the initial development efforts toward creating the Seam 3 JMS module.  As more functionality is built, more tests will be written, so look to this module as a source of ideas for how to use Arquillian.


    One of the features I'm looking forward to in Arquillian is the ability to include additional libraries in the test deployments. Hopefully that gets fixed soon!


    Stay tuned for more developments on Seam 3 at and keep watching the Arquillian of the announcement for the Alpha1 release!