In Relation To

Today we are happy to announce the 5.0.1.Final release of Hibernate Validator. In case you are wondering what happened with 5.0.0.Final - it has not gone missing. In fact it was released on the 11th of April.

Hibernate ORM 4.3.0.Beta2 was just released. The full changelog can be viewed here

I am pleased to announce the release of Weld 2.0.0.Final, the reference implementation of Contexts and Dependency Injection for Java EE 1.1 (JSR 346). For a list of major changes in CDI 1.1 see the specification.

Hibernate ORM 4.2.1.Final and 4.1.12.Final were just released. The full changelogs can be viewed here: 4.2.1.Final and 4.1.12.Final

The Hibernate Search 4.3 iteration reached its first milestone: version 4.3.0.Alpha1 is now available for download from Sourceforge.net and Maven repositories.

Continuing with our monthly releases, we’re happy to announce new 1.0.0.Beta4 release.

Previously, setting up a Hibernate ORM development environment in Eclipse was a pain. Many of you have complained about circular dependencies, generated sources not added to the classpath, etc. We recently cleaned up the 'gradle eclipse' task in HHH-7617 (1). If you're interested in getting started with Hibernate contributions, here's the easiest way to do it. Note that this requires 4.2.1-SNAPSHOT, 4.3.0-SNAPSHOT, or later:

At flush-time, Hibernate needs to know what entity state has become dirty (changed) so that it knows what data needs to be written to the database and what data does not. Historically Hibernate only defined one means of such dirtiness checking, but has since added multiple additional schemes which seem to be not as well known. The intent for this blog is to start a base for improving the documentation around dirty checking and these various options.

The Hibernate team is pleased to announce today's release of Hibernate 4.3.0.Beta1 which targets the (still not finalized) JPA 2.1 specification which is part of the upcoming Java EE 7 platform. This is the first release targeting JPA 2.1 support. As mentioned, JPA 2.1 is not completely finalized so this support should be considered a preview. JPA 2.1 defines a number of enhancements. I won't go in depth in each of them here as I plan to follow up with separate in-depth blog posts for some of these features. However, the web abounds with good summaries of the new features; for example:

The soon-to-be final JPA 2.1 specification adds standardized support for dealing with JDBC CallableStatements (stored procedure and function calls). Arun Gupta has a decent summary of the initial JPA 2.1 features, including Stored procedure support, at https://blogs.oracle.com/arungupta/entry/jpa_2_1_early_draft. Standardized here means both across providers as well as across database vendors. Pretty sweet. As much as I liked the idea of standarized support for handling callable statements, I was not overly thrilled with certain aspects of the proposed JPA StoredProcedureQuery API. My worries were mainly around how the outputs were accessed, especially when multiple results are expected. Let's first look at a simple example of a procedure returning a result: