In Relation To

The release cycle of Hibernate Search 4 has begun. Alpha 1 is out. We already have many things implemented so this change is consistent and more releases will come quickly.

In my previous blog I wrote about what the role of the Java Connector Architecture (JCA) container is inside the JBoss Application Server - and especially the IronJacamar container inside JBoss Application Server 7.

Hibernate Core 3.6.7.Final is a maintenance release with just a couple of fixes.

Haha! Try compiling this Java code:

Unless you've been living under a rock for the past week, then you'll have seen that Red Hat just added support for JBoss AS 7 on OpenShift (both Express and Flex).

This is a gorgeous, perfect example of precisely how not to engage in debate over technical issues. I won't respond point-by-point, because the post is mainly self-refuting, but it does amuse me to highlight the following:

A couple of days ago I spotted an interesting hole in Ceylon's type checker. I started out with something like this:

Hibernate Core 4.0.0.Beta5 has just been released. The complete list of changes can be found in JIRA release notes. Things are moving along with the main focus on the new metamodel and its integration into the Core engine.

In connection with this discussion it's worth making explicit what I guess everybody knows, but that sometimes seems to get a bit mixed up in conversation: that Java's support for raw types (necessary for backward compatibility with pre-generics code) doesn't really have anything much to do with type argument erasure. In a hypothetical language: