Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Jakarta Data with Hibernate #33415

Closed
hantsy opened this issue Aug 22, 2024 · 1 comment
Closed

Support Jakarta Data with Hibernate #33415

hantsy opened this issue Aug 22, 2024 · 1 comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: declined A suggestion or change that we don't feel we should currently apply

Comments

@hantsy
Copy link
Contributor

hantsy commented Aug 22, 2024

Hibernate 6.6 supports Jakarta Data 1.0 and utilizes Hibernate modelgen tools to generate the Repository implementation source codes at Java compile time. It is a good match with Spring AOT, no need to transform the Jakarta Data related facilities.

I wrote a post about Spring and Jakarta Data integration before, check https://medium.com/itnext/integrating-jakarta-data-with-spring-0beb5c215f5f

  1. Scan Jakarta Data @Repository as beans
  2. Allow Spring @Repository to interoperate the Jakarta Data one
  3. Allow developers to use Jakarta @Transactional or Spring @Transactional(requires support Hibernate StatelessSession)
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Aug 22, 2024
@sdeleuze sdeleuze added in: data Issues in data modules (jdbc, orm, oxm, tx) status: waiting-for-internal-feedback An issue that needs input from a member or another Spring Team labels Sep 4, 2024
@jhoeller
Copy link
Contributor

jhoeller commented Oct 9, 2024

For 7.0, we might reopen #7184 for basic StatelessSession management but won't go as far as providing Jakarta Data support in Spring Framework proper. It looks like this does not fit with the Spring Data project either, so it'll be left to community efforts.

@jhoeller jhoeller closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2024
@jhoeller jhoeller added status: declined A suggestion or change that we don't feel we should currently apply and removed status: waiting-for-triage An issue we've not yet triaged or decided on status: waiting-for-internal-feedback An issue that needs input from a member or another Spring Team labels Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

No branches or pull requests

4 participants