22. Jan 2014
16. Dec 2013
05. Dec 2013
20. Nov 2013
09. Oct 2013
12. Sep 2013
29. May 2013
10. Apr 2013
03. Apr 2013
06. Sep 2012
04. Apr 2012
08. Mar 2012
09. Feb 2012
24. Jan 2012
I have just released 4.3.1.Final, the first bugfix release for Hibernate ORM 4.3. In addition to bug fixes, a few improvements of note include:
- HHH-5289 : Improved performance of reflection calls
- HHH-6911 : Allows reading and writing @DiscriminatorValue from/to @DiscriminatorColumn when combined with InheritanceType.JOINED (for portability with providers which need DiscriminatorColumn)
- HHH-8865 : Added a new guide on logging to the growing set of topical guides. This is the first know documentation of any sort on using/configuring JBoss Logging, and also discusses some of the more good-to-know specific logging categories. See http://docs.jboss.org/hibernate/orm/4.3/topical/html/logging/Logging.html
See the release page for details of all changes.
Artifacts can be found in the usual places.
The Hibernate team is proud to announce the Hibernate ORM 4.3.0.Final Release. With this release, Hibernate is now a certified implementation of the JPA 2.1 specification. Certified awesomeness!
A lot of work has gone into this release over the last few months. The main focus of 4.3 was JPA 2.1 support, so much of the work these past few months focused on new JPA 2.1 features. The new features defined for JPA 2.1 include:
- Support for stored procedures. See my previous blog for details
- CriteriaUpdate and CriteriaDelete allow definition and execution of UPDATE and DELETE queries in type-safe Criteria form.
- Entity listeners can now take advantage of dependency injection through CDI.
- AttributeConverters, which define the ability to apply conversions on basic values between their database representation and their representation in your domain model. This is similar in concept to Hibernate's Type contract, although certainly less powerful (can only apply to basic values and operate on in-memory values). On the positive side, JPA AttributeConverters are portable across providers.
- Entity Graph support
- Standardized schema generation. With 2.1 JPA now defines schema generation which is standardized across providers in terms of how generation is performed and the settings providers understand as a baseline. Arun Gupta has a good write up of the basic schema generation support.
- Synchronization of persistence contexts via SynchronizationType
- @ConstructorResult support in result set mappings for native queries
The significant non-JPA work that has gone into 4.3 includes:
- Continued improvement in Hibernate's support for OSGi environments. OSGi support in 4.3 is still somewhat bound by certain design limitations within Hibernate, We plan to fully address these limitations in 5.0 (see HHH-8501 for details).
- Continued work on new bytecode enhancement support within Hibernate, adding support for
inline dirty checking. See HHH-8354 for details.
- Initial break down of the monolithic DocBook-based manuals into smaller Asciidoc-based topical guides (HHH-8606). This is an ongoing process.
The full change log for the release can be seen at https://hibernate.atlassian.net/browse/HHH/fixforversion/15150.
In 2 weeks we'll decide whether a CR3 is needed or release Final at that time.
Thanks for all the feedback!
The Hibernate team is proud to announce the 4.3.0.CR1 release of Hibernate ORM. This is the first release candidate for 4.3 and JPA 2.1 support. For those who maybe are not familiar with our release methodology, this means that in 2-3 weeks this release will essentially be re-tagged as Final unless some critical bugs are reported with it in the meantime.
I will do a full break down of all the new goodies added over the course of 4.3 development in the Final release announcement. Specific development of note done for CR1 include:
- Support for JPA 2.1 EntityGraphs. This was the biggie holding us back from going to CR. HHH-8285 and friends
- Integration of the Hibernate JPA Static Metamodel Generator into the ORM project - HHH-8483
- Starting on break down of the monolithic DocBook-based manuals into smaller Asciidoc-based topical guides (ongoing) - HHH-8606
- A number of performance fixes including HHH-8709, 8704, 8698, HHH-8682, etal.
The full version info (including change log) can be seen on the version page
Artifacts and release bundles can be found in the normal places.
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
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 enhancementwork 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 enhancementenhancements 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!
|Showing 1 to 5 of 73 blog entries||