Jakarta Data and Jakarta Persistence
summary
Jakarta Data 1.0 and Jakarta Persistence 3.2 deliver a new type safe persistence model implemented in Hibernate 7 as Hibernate Data Repositories that uses compile‑time validation via annotation processing to turn annotated interfaces into tiny generated implementations. Repositories are stateless CRUD by default with optional access to a stateless session, JQL (a JPQL subset) is syntax‑and‑type‑checked at compile time, CDI events fire with transaction phase awareness, projections and records mapping are supported, and a proposed entity agent (stateless entity manager) plus optional reactive Uni return types address stateful and reactive use cases.
AI-written summary · about
chapters (11)
- 0:00Introduction to Jakarta Data
- 0:44Critique of repository patterns
- 6:50Rethinking the repository model
- 10:41Getting started with Jakarta Data
- 13:36Defining query methods
- 17:15Query languages and dynamic queries
- 20:58Entities, records, and relationships
- 26:04Jakarta Data 1.1 features
- 29:48Projections and metadata
- 32:02Future vision and roadmap
- 38:53Q&A and closing
related talks
50mJakarta Data and Jakarta Persistence
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
26mUnlocking Data Access Excellence with Jakarta Data
47mJakarta EE 12 and the future of Java persistence
49mUnlocking Data Access Excellence with Jakarta Data
48mManaging Data in Jakarta EE Applications
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
46mThe State of Java Relational Persistence