In Relation To

Back to home

Hibernate ORM 4.3.0.Beta5 Release

Posted by    |       Hibernate ORM JPA Releases

Version 4.3.0.Beta5 release of the Hibernate ORM project has just been released. This is a step closer towards JPA 2.1 compliance, but also lots of other goodies. JPA 2.1 work of note includes:

  • HHH-8478 - which should complete AttributeConverter support.
  • HHH-8445 - which adds support for REF_CURSOR parameters and should complete StoredProcedureQuery support.
  • HHH-8276 - which was the major prerequisite step for entity graph support. You'll be using that anytime you load entities directly or by to-one association.
  • HHH-8523 - which improves support for parameters and returns using an explicit TemporalType and defined as Calendar

Entity graph support is still not complete, but as mentioned above most of the necessary prerequisite work has been covered now under HHH-8276 and HHH-7841.

Non JPA 2.1 work of note includes:

  • HHH-8476 - which now manages associated many-to-many table rows with bulk deletes (HQL/JPQL)
  • HHH-7689 - which implements better clean up of JDBC batches during failed transactions. The previous behavior led to problems in the way Spring attempts to reuse Sessions after exceptions (which is technically not supported, but this was a good change to make anyway)
  • HHH-8354 - which adds on top of the new bytecode enhancement work to weave in in line dirty checking. In other word, we now have the ability to have entities and embeddables track their own state changes (via enhancement) and for Hibernate to leverage that knowledge during flush. This is still very young, but promises to significantly reduce flush times in many use-cases. We'll have more announcements about all the bytecode enhancement enhancements later.
  • HHH-8520 - ability to use the hibernate.globally_quoted_identifiers with HBM mappings

The full changelog can be found in Jira at https://hibernate.atlassian.net/browse/HHH/fixforversion/14250. Artifacts can be found in the usual places.

Beta6 is scheduled in Jira already following the normal 4 week time box, however be aware that that release is likely to not happen on that particular day; its more likely to be the week before or the week after as I am traveling that particular week. I'll keep Jira up to date as we go along.

Thanks for the support and contributions!

Back to top