Jakarta Data and Jakarta Persistence
summary
Jakarta Data 1.0 plus Jakarta Persistence 3.2 deliver a more typesafe persistence model that Hibernate 7 already implements: annotation processing generates compile‑time checks so repository method parameters must match entity fields and JQL annotations are validated, avoiding runtime errors. Repositories are stateless in this model and map to a stateless session (including an efficient upsert), the spec emits a static meta‑model (underscore classes) for type‑safe sorting/projections, and JPA 3.2 adds Java boot for EntityManagerFactory, a schema manager, and type‑safe named queries and entity graphs.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:50Why I was wrong about repositories
- 10:55Jakarta Data introduction
- 17:06Jakarta Data repository interface
- 26:07Jakarta Persistence 3.2 updates
- 32:06Future of Jakarta Data and Persistence
- 42:33Q&A session
related talks
50mJakarta Data and Jakarta Persistence
47mJakarta EE 12 and the future of Java persistence
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
26mUnlocking Data Access Excellence with Jakarta Data
46mThe State of Java Relational Persistence
49mUnlocking Data Access Excellence with Jakarta Data
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
48mA Developer's Guide to #JakartaEE 11