Being productive developer using JPA helper libraries
summary
Shows how DeltaSpike Data generates CDI repository implementations from interfaces and method-name conventions so CRUD and simple findBy... queries work without JPQL, requires exposing EntityManager as a CDI producer and using container-managed transactions via a stateless façade. Demonstrates paging, query-by-example, and falling back to @Query or named queries for complex cases. Recommends QueryDSL for readable, type-safe dynamic predicates with generated Q classes via an annotation processor. Recommends Spring Data on Spring stacks, DeltaSpike on Java EE.
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:30Presentation
- 5:23What I dont like
- 7:15What I miss
- 7:48I dont blame JPA
- 9:13How I came to this
- 10:03Special methods
- 11:35Clean up
- 12:17Print Data
- 12:39Delta Spike Data
- 12:53Repository Principles
- 14:51DeltaSpike Data
- 16:08Using DeltaSpike Data
- 17:24Configuring the dependencies
- 26:07paging
- 26:47pureresult
- 27:28naming convention
- 27:56name query
- 28:52lava spike
- 29:11cure diesel
- 29:22it kind of creates
- 29:44for more complex stuff
- 30:21programmatic approach
- 30:40CureDiesel
- 30:50Java Collections
- 33:46Maven
- 34:49Which one to use
- 35:33Which one to use when
- 36:33Conclusion
related talks
01h 32mSpring Data Repositories -- A Deep Dive
50mSpring's unexpected features
49mExtending Spring Data
49mUnlocking Data Access Excellence with Jakarta Data
49mPerformance oriented Spring Data JPA & Hibernate
48mManaging Data in Jakarta EE Applications
46mThe State of Java Relational Persistence
44mPerformance oriented Spring Data JPA & Hibernate