Tags
Authors
Hibernate Reactive 2.3.0.Final is now available!
This release is compatible with Hibernate ORM 6.5.0.Final and support for soft deletes.
The full list of changes is available on GitHub.
6.5 has gone final!
I had so many interesting new things to talk about in the summary of Jakarta Persistence 3.2 that I forgot to mention an important thing we’re taking away.
Hibernate ORM version 6.5
already received a couple candidate release versions, and a final release will follow shortly. This post highlights one of the improvements that comes with this version: efficient retrieval of non-identifier database generated values.
Jakarta Data is a new specification for persistence in Java, scheduled for release as part of the EE 11 platform. In a previous post I introduced the basic features of a Jakarta Data repository, with a strong emphasis on how Jakarta Data provides compile-time type safety, enabling static analysis performed by an annotation processor.
This involved moving some information that used to be expressed in procedural code into:
-
annotations like
@Query
and@Find
, and -
the names and types of repository method parameters.
Today we’re going to talk about some more dynamic features of Jakarta Data. You might anticipate that these would come with a loss of type safety, but we’ve found a way to avoid that. The essential ingredient is a static metamodel.
6.5 brings many new features, in addition to many improvements and fixes.
We are pleased to announce the releases of Hibernate Search 7.1.1.Final, 7.0.1.Final and 6.2.4.Final.
While these releases are mainly to address some minor documentation discrepancies, they also bring compatibility with newer versions of Elasticsearch and OpenSearch and a few bugfixes.