In Relation To

Kind of knew people would ask about this... So why did we decide to deprecate CGLIB support in Hibernate? First I want to point out that Hibernate and CGLIB have a very long history (and a largely good history) in terms of working together. This is not an indictment against any of the CGLIB developers. They are good guys and as I stated above for many years Hibernate and CGLIB have worked well together.

Today we have released both 3.5.5 and 3.6.0.Beta3.

Gunnar asked me an interesting question on Bean Validation. Instead of keeping the knowledge private, I thought it would be useful to share more wildly.

The Hibernate team is happy to announce the availability of the 3.6.0.Beta2 release. The major change from Beta1 is the merging of AnnotationConfiguration into Configuration (HHH-5375). AnnotationConfiguration is now completely deprecated.

Just a heads up to everyone - I'll be updating the seamframework.org wiki software very shortly. Downtime is currently expected to be around 20 minutes, once the site is back up I'll post an update here.

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

While working on Hibernate Search 3.3, we have discovered a critical issue with Hibernate 3.2. If you use Hibernate Core 3.5 in a JTA environment (recommended), the way Hibernate Search 3.2 registers itself can lead to inconsistent indexing and generate assertion failures. All this is fixed in Hibernate 3.2.1 which you can get here and ported to trunk as well. We have also added tests to cover the JTA area.

The Hibernate team is happy to announce the availability of both the 3.5.4 and 3.6.0.Beta1 releases.