I'm happy to announce the first beta release of IronJacamar 1.0 which implements the Java EE Connector Architecture 1.6 specification.

Full release notes are here.

IronJacamar

We have rebranded the project to IronJacamar, since JBoss JCA was simply too boring a name.

This means of course that we have changed our web site and documentation URLs.

Certified

We have certified the Beta1 release against the Java EE Connector Architecture 1.6 TCK, which means that the release implements Chapter 3.5 of the specification.

This basically means that full outbound communication is supported, so we want to hear about your success with the release.

The distribution also features all of our extensions and tools

• Embedded environment with ShrinkWrap support
• Arquillian support for the embedded environment
• Validator chain for resource adapter archives
• Code generator which can generate a full development environment including a test suite

So check out our documentation on how to get started !

The Road Ahead

We are now working on integrating the container into the upcoming JBoss Application Server 7.0 release series and of course we will keep enhancing the distribution and our tools.

For Those About to Rock, We Salute You !

[WebSite] [Download] [Documentation] [JIRA] [Forum]

I'm happy to announce the 13th developer snapshot release of JBoss JCA 1.0.

Full release notes are here.

Security integration

The initial security integration with the container is now done.

We have added the possibility to specify users and roles in property files under the config directory.

This means that you can now execute your javax.resource.spi.work.Work instances under a security context and make use of the JSR-196 callbacks as specified in the JCA 1.6 specification.

We will be looking at adding additional security integration plugins in future releases.

Arquillian support

Look Ma' Space Aliens !

We have added integration with the Arquillian project in our embedded JCA container setup. This allows an even easier unit test setup than before.

An example would be

package org.jboss.jca.embedded.unit;

import org.jboss.jca.embedded.rars.simple.MessageListener;
import org.jboss.jca.embedded.rars.simple.TestActivationSpec;
import org.jboss.jca.embedded.rars.simple.TestConnection;
import org.jboss.jca.embedded.rars.simple.TestConnectionFactory;
import org.jboss.jca.embedded.rars.simple.TestConnectionInterface;
import org.jboss.jca.embedded.rars.simple.TestConnectionManager;
import org.jboss.jca.embedded.rars.simple.TestManagedConnection;
import org.jboss.jca.embedded.rars.simple.TestManagedConnectionFactory;
import org.jboss.jca.embedded.rars.simple.TestResourceAdapter;

import java.util.UUID;

import javax.annotation.Resource;

import org.jboss.arquillian.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.logging.Logger;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.JavaArchive;
import org.jboss.shrinkwrap.api.spec.ResourceAdapterArchive;

import org.junit.Test;
import org.junit.runner.RunWith;
import static org.junit.Assert.*;

/**
 * Unit test for Arquillian integration
 * 
 * @author <a href="mailto:jesper.pedersen@jboss.org">Jesper Pedersen</a>
 */
@RunWith(Arquillian.class)
public class ArquillianTestCase
{
   // --------------------------------------------------------------------------------||
   // Class Members ------------------------------------------------------------------||
   // --------------------------------------------------------------------------------||

   private static Logger log = Logger.getLogger(ArquillianTestCase.class);

   private static String deploymentName = "ArquillianRA";

   /** The resource adapter */
   @Resource
   private TestConnectionFactory cf;

   /**
    * Define the deployment
    * @return The deployment archive
    */
   @Deployment
   public static ResourceAdapterArchive createDeployment()
   {
      ResourceAdapterArchive raa =
         ShrinkWrap.create(ResourceAdapterArchive.class, deploymentName + ".rar");

      JavaArchive ja = ShrinkWrap.create(JavaArchive.class, 
                                         UUID.randomUUID().toString() + ".jar");
      ja.addClasses(MessageListener.class, TestActivationSpec.class, TestConnection.class,
                    TestConnectionFactory.class, TestConnectionManager.class, 
                    TestConnectionInterface.class, TestManagedConnection.class, 
                    TestManagedConnectionFactory.class, TestResourceAdapter.class);

      raa.addLibrary(ja);
      raa.addManifestResource("simple.rar/META-INF/ra.xml", "ra.xml");

      return raa;
   }

   //-------------------------------------------------------------------------------------||
   // Tests ------------------------------------------------------------------------------||
   //-------------------------------------------------------------------------------------||

   /**
    * Basic
    * @exception Throwable Thrown if case of an error
    */
   @Test
   public void testBasic() throws Throwable
   {
      assertNotNull(cf);
   }
}

So when your boss ask you why you havn't got a proper test suite for the resource adapter -- what are you going say ?!?

Code generator

Our code generator have seen a lot of updates this month adding full support for all JCA specifications, and it now even creates a test suite setup for the resource adapter.

The code generator now has the following features

• JCA 1.6 using annotations
• JCA 1.6 using metadata
• JCA 1.5
• JCA 1.0
• Test suite
• Apache Ant build environment

We will keep adding more features in our next releases, but be sure to send us your feedback on its usability.

Container changes

Our Jetty integration have been moved to the system directory in the container layout to allow an easy way to uninstall this feature if you don't need it.

We have upgraded the version of Jetty to 7.1.4 to keep up with its development.

The Road Ahead

This release brings us a lot closer to our first Beta release of the project :) We still have a couple of TODOs that needs to be fixed, but we are pushing hard to get the release out.

See ya' @ JUDCon on Monday !

For Those About to Rock, We Salute You !

[WebSite] [Download] [JIRA] [Forum]

I'm happy to announce the 12th developer snapshot release of JBoss JCA 1.0.

Full release notes are here.

Code generator

The work on the code generator continued during this development cycle and we now have a functional generator for JCA 1.6 archives. So feel free to try it out and send us feedback.

The work will continue with JCA 1.0 and JCA 1.5 support and adding more features to help developers getting starting with JCA development.

Scoped deployments

The resource adapter deployer now allows you to set if the deployments should be scoped (isolated) and thereby allow use of libraries of a different version already included in the standalone distribution.

JUDCon

I'll be speaking at JUDCon where you can get an overview of JCA 1.6 and the project. You can catch a preview of the talk from the latest Boston JBoss User Group presentation.

Remember to sign up for our HackFest too !

For people who like food and beer: sign up for a Boston JBoss User Group event special on Sunday June 20th: Let's Get Ready to Rumble !.

The Road Ahead

We are looking at our security integration and integration with Arquillian, so look for changes in these areas soon.

For Those About to Rock, We Salute You !

[WebSite] [Download] [JIRA] [Forum]

I'm happy to announce the 11th developer snapshot release of JBoss JCA 1.0.

Full release notes are here.

Code generator

This snapshot saw the introduction of our new resource adapter code generator.

The code generator will provide developers with a resource adapter code skeleton from which they can bootstrap their development.

Currently the focus is on

• Resource adapter with JCA 1.6 annotations
• Apache Ant build environment

but we planning to support all versions of the spec as well as Apache Maven build environments.

If you are interested in helping out with this task, feel free to drop by our forum.

Presentations

I'll be speaking at

• Boston JBoss User Group May 11
• JUDCon June 21

both in Boston, so register today !

Also; feel free to checkout my DZone article.

The Road Ahead

The EE6 TCK is still our priority, so we will continue down that road - but be sure to send us feedback on your use-cases.

For Those About to Rock, We Salute You !

[WebSite] [Download] [JIRA] [Forum]

I have put up the videos from our last couple of meetings at the Boston JBoss User Group.

So feel free to checkout:

• EJB 3.1 and testing by Andrew Lee Rubinger
• Java EE 6 and JBoss AS 6 by Shelly McGowan and Scott Marlow

Our next meeting will be

• Java Connector Architecture 1.6

on May 11th where I'll present the spec and the JBoss JCA project.

Hope to see you there !