Following the "release early, release often" motto, here comes a new version of Hibernate Validator, 6.0.9.Final.
It brings some nice improvements and fixes a couple of bugs.
This is a recommended upgrade for everyone using Hibernate Validator and it is a drop-in replacement of 6.0.8.Final, except if you already started to use the new constraint validator payload feature (see below).
Hibernate Validator 6.0 has matured a lot since its first release, last August.
We added a couple of new features but we also invested a lot of work in improving the overall performances.
I published a first blog post last October to share an update about our performance work based on 6.0.4.Final.
We just released 6.0.8.Final and have a couple more improvements baked for our next release so it’s definitely time for an update.
It has been a couple of months since our last Hibernate Validator release and we have made some significant progress since then.
We just released Hibernate Validator 6.0.8.Final containing all these bugfixes and enhancements.
This is a recommended upgrade for everyone using Hibernate Validator 6.0.x and it is a drop-in replacement of 6.0.7.Final.
The most significant feature in Bean Validation 2.0 (JSR 380) is the support for container element constraints.
I.e. you can now apply constraints to the contents of container types such as
Optional by annotating their type arguments
(which became possible with Java 8):
List<@Future LocalDate> shipmentDates.
In this blog post you’ll learn how to take advantage of that for the validation of custom container types,
Graph from Google’s widely known Guava library.
We used to be very conservative on the constraints included in Hibernate Validator but we changed this policy recently and we would like to have more constraints built-in.
Of course, we won’t accept everything: the proposed constraints needs to be of general usage and well defined but the idea is to have more features in Hibernate Validator out of the box.
This post will be useful to those who have some interesting custom Bean Validation constraints and want to share them with the community.
[ ... ]
We just released the 6.0.7.Final version of Hibernate Validator containing a couple of enhancements.
This is a recommended upgrade for everyone using Hibernate Validator 6.0.x and it is a drop-in replacement of 6.0.5.Final.
We just released the 6.0.5.Final version of Hibernate Validator containing a couple of important bugfixes and some enhancements.
This is a recommended upgrade for everyone using Hibernate Validator 6.0.x and it is a drop-in replacement of 6.0.4.Final.
Hibernate Validator is not the only Bean Validation implementation out there, we have one (friendly) competitor called Apache BVal.
Apache BVal has not caught up with Bean Validation 2.0 yet but, as the last benchmark in the Bean Validation field is dated from 2010 (remember "Machete don’t text"?), I thought it was high time to revisit this benchmark and get some fresh numbers.
Especially with all the optimization work we made for 6.0.
Another week, another Hibernate Validator release. You might ask why we release a new maintenance version of the 6.0 branch so soon: it is mostly to provide a patch for WildFly 11 Final but it is also packed with nice enhancements!
This is a recommended upgrade for everyone using Hibernate Validator 6.0.x and it is a drop-in replacement of 6.0.3.Final.
And here comes another maintenance release of Hibernate Validator 6.0.
A lot of thanks to our users and contributors for reporting issues and submitting pull requests, it was definitely a great team effort.
This is a recommended upgrade for everyone using Hibernate Validator 6.0.x and it is a drop-in replacement of 6.0.2.Final.