Hibernate ORM 4.2.20.Final was released 24-July-2015. At the time it was released,
SourceForge was out of commission so distributions could not be uploaded. I decided
to delay the announcement until SourceForge was back in commission and I was able
to release 4.3.11.Final on 5-Aug-2015.
Today I released a fourth candidate release for Hibernate ORM 5.0 (5.0.0.CR4). The purpose was entirely to change the defaults
for some settings. This allowed some additional fixes and additional documentation work to make it in.
While Hibernate ORM applies some more polish before releasing the final version,
so did the Hibernate Search team.
Hibernate Search version 5.4.0.CR2 is now available!
It was built and tested with Hibernate ORM 5.0.0.CR3, again we’re just waiting for that to be final but decided
to release another Candidate Release as some fixes and improvements were recently applied.
Yesterday I released the third candidate release for Hibernate ORM 5.0 (5.0.0.CR3). We felt another CR was warranted
because we had some minor integration (SPI) work that we needed to make in to Final, but too much development had happened since
the second CR to be considered risk free to just include everything into Final. At any rate CR3 got lots of great TLC :) The
complete set of changes can be seen in the Jira changelog. The
main changes include:
I know you have been waiting in anticipation, but now it is available -
Hibernate Validator 5.2.1.Final :-). Given that it is a drop-in replacement for
all 5.x releases, there is no reason to delay an upgrade. Just go and
For the more cautious, here again the highlights of the 5.2 release with
pointers to more information.
The other day I came across an interesting mapping challenge which I thought may be worth sharing. If you are a seasoned JPA user, it will probably be nothing new to you, but those not as experienced may find it helpful :)
TL;DR - JPA let’s you override database columns for embedded objects but also for collections of embedded objects; @AttributeOverride and @AssocationOverride can be used for that.
Let’s assume the following entity model representing a person and their home and business address: