I'm happy to announce the 2nd beta release of the IronJacamar 1.1 series.
The full release notes are here.
In this release we took a hard look at how resource adapter development is done, and what it would take to be more productive. The previous releases of IronJacamar have featured an embedded environment, and various tools to help you get started. But more was needed in our view.
First we got rid of the requirement to have an on-disk representation of the IronJacamar deployment descriptors. So now you are able to deploy a ShrinkWrap/Descriptor instead for all these XSDs.
Next was the ability to test your resource adapter in error scenarios such that you are sure that it'll behave correctly. For this we integrated the Byteman tool in the embedded environment.
Then, the biggest problem in resource adapter development: Access to the Enterprise Information System (EIS). An EIS can be large installation, and in many cases it isn't really suited to run as part of a developer test suite run, since they don't really integrate well with embedded unit testing. So we have included an EIS test server in our distribution where you can implement a
Handler interface that mocks the communication protocol of the EIS in order to make your smoke tests pass without an actual EIS installation. The EIS test server can run in Apache Ant, Apache Maven and standalone environments, so you should be covered in most cases. Otherwise let us know. Our code generator of course knows how to handle the integration, so you can check it out that way. And I'm not saying that using the EIS test server is enough for your resource adapter to go into a real test or production environment; it is a help for resource adapter developers, not a golden bullet.
Finally we upgraded the libraries used for our embedded platform in order to get the latest fixes.
You can find more information here:
And our Eclipse plugin have been verified on Eclipse 4.2 (Juno) to top it off :)
DistributedWorkManager on steroids
The DistributedWorkManager saw a big update in this release.
Our policy module was updated with a
WaterMark implementation, which will look at how many free threads are available to the local WorkManager. The default setup is a value of 0, which will start to distribute Work instances once there are no free threads locally.
Our selector module got a
MaxFreeThreads implementation, which will select the DistributedWorkManager in the cluster with the most free threads available for execution.
The real kicker was the addition of a JGroups based transport, which will allow you to configure the cluster parameters in much more detail taking IronJacamar into NFL. No more college football here.
Now that we have all the core modules, we will focus on implementation details that will tackle more advanced scenarios of distribution and thread management.
And the core WorkManager implementation also saw numerous fixes to align it more against the specification text.
There were other improvements in this release:
- Updates to our validator tool
- Major updates to our resource adapter information tool
- Updates to the JDBC resource adapter, especially in the reauth area
- Added support for deploying to a remote IronJacamar installation
The Road Ahead
In short - it is full speed ahead !! We now got THE best platform for resource adapter development - prove us wrong ! This will enable us to get our new features tested and verify your reports about potential bugs at a quicker speed.
With EE7 getting closer we will focus in a higher degree on getting IronJacamar 1.1 ready for certification, and making sure that all of the specification is covered.
IronJacamar 1.1.0.Beta2 will be our last release on Java SE 6 - the time has come to move to Java SE 7.
For Those About to Rock, We Salute You !
[WebSite [Download] [Documentation] [JIRA] [Forum]