In Relation To

Infinispan and Seam are doing it again. We're hosting a community social in the midst of Europe's premier Java conference, Devoxx (in Antwerp, Belgium). This year we'll be joined by Arquillian to keep things under control (you don't want to make Ike mad).

Hibernate has moved to Git (hosted on GitHub) for source control. That has been well documented. I wanted describe the approach Hibernate takes to branching, versioning and releasing as it is something that has come up a number of times, even prior to the move to Git.

What with just getting back from vacation, I forgot to post that I will be speaking tomorrow (Thursday 10th) evening in Belgium on CDI, Java EE 6 and Arquillian as a guest of the Belgium JBoss User Group. More here.

As AS6 has been getting closer to CR, we have recently started working on our new next generation application server. Last week, we just released an early alpha of this work, 7.0.0.Alpha1, code named Halloween.

Hibernate Search 3.3 CR1 is out. Last chance for testing before the baby goes out. This release include many bug fixes and small features but we have added a couple of significant ones:

Hibernate Metamodel Generator 1.1.0.Final is now available for download either from the JBoss Maven repo or from SourceForge.

Seam Faces - Version 3.0.0.Beta1 is released. Several bugfixes as well as several new features have been included. This new version requires Weld Version 1.0.1.Beta1 or later. (Meaning GlassFish 3.1 or JBoss AS 6 M5+)

Hibernate Search 3.3.0.Beta3 is out with 12 freshly squeezed bugs. See the Jira release notes for a full list. Some of the more notable changes are:

Quite a few people have asked me recently if they have to wait until EAP 6 before they can use CDI in a supported JBoss application server. The good news is, no they don't! While there isn't currently any productised offering for CDI itself (i.e. it's unsupported), it is still possible to use it as the component framework for your EAP-based application thanks to the Weld-servlet library. What's even better is that it requires absolutely no configuration changes to the default EAP installation - CDI based applications can be deployed straight to it and will work out of the box.

I'm happy to announce that the IronJacamar team have released 1.0.0.Beta3 of the container which implements the JCA 1.6 specification.