Today we released the first milestone build of Jakarta Persistence 4.0.



Jakarta Persistence—​more commonly known as JPA—​defines the industry standard for management of persistence and object/relational mapping in Java.
It’s the most widely used persistence solution in the Java ecosystem and by far the most successful object/relational mapping API in any programming language.
JPA4 is easily the most significant revision of the specification since JPA 2.0 was released in December 2009.



This milestone build is being made available for wider community review with the purpose of collecting feedback from users and implementors.
Remember: now is the time to send feedback.
JPA 4 is still not feature complete, and none of the changes I’m about to describe are set in stone.
Don’t wait for the specification to go final later this year before trying it out.



Let’s see what’s new in this release.

Hibernate Blog

Jakarta Persistence 4.0 Milestone 1 has been released for community review. Key additions include EntityAgent for direct database operations bypassing the persistence context, @StaticQuery annotations with compile-time type checking, a programmatic ResultSetMapping API, and the long-awaited ability to set LAZY as the default fetch type for to-one associations. The release also introduces Statement interface for DML operations, new get()/findMultiple()/getMultiple() methods, TypedQuery.getResultCount(), optional 'select new' syntax for record projections, @ExcludedFromVersioning, programmatic lifecycle listener registration, improved named entity graphs, and standardized JDBC fetch/batch size properties. This is described as the most significant JPA revision since 2.0 in 2009, and is part of a broader effort alongside Jakarta Data and Jakarta Query specifications.

In Relation To