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

Is there any plan to implement jakarta data? #35603

Closed
JackyAnn opened this issue Aug 28, 2023 · 8 comments
Closed

Is there any plan to implement jakarta data? #35603

JackyAnn opened this issue Aug 28, 2023 · 8 comments
Labels
area/persistence OBSOLETE, DO NOT USE kind/enhancement New feature or request triage/wontfix This will not be worked on

Comments

@JackyAnn
Copy link

Description

https://github.com/jakartaee/data

Implementation ideas

No response

@JackyAnn JackyAnn added the kind/enhancement New feature or request label Aug 28, 2023
@geoand geoand added area/persistence OBSOLETE, DO NOT USE and removed triage/needs-triage labels Aug 29, 2023
@geoand
Copy link
Contributor

geoand commented Aug 29, 2023

cc @Sanne @gavinking

@Sanne
Copy link
Member

Sanne commented Aug 29, 2023

No we don't have any plans to implement this spec; in fact our team was exploring some ideas which we believe would be much better; it's too early to say for sure but I'm surprised they'd vote positively for such a spec to be cast in stone when there's many interesting ideas floating around, and in its current shape when there's essentially a single implementation, and fairly ancient now - I'd expect even the people who came up with the original idea would be eager to improve by now, there are several lessons to learn from and it should be clear to anyone that one can do better nowadays - especially in Quarkus and other novel frameworks which can analyze the whole world at build time.

But if anyone wants to provide a Quarkus extension in the quarkiverse, that's totally cool of course ;)

Just don't expect my team to spend time on it: we need to prioritize very carefully what we can afford to spend time on, and we won't spend time on endeavours we don't even believe in.

@Sanne Sanne closed this as completed Aug 29, 2023
@geoand geoand added the triage/wontfix This will not be worked on label Aug 29, 2023
@gavinking
Copy link

I mean from my point of view I feel like this spec is attempting to very belatedly set in stone a rather antiquated design right at the moment when this space has started moving again and advances in the Java language have made new approaches possible.

In the Hibernate community and in the JPA group we're doing a lot of work on enhancing typesafety compared to these older approaches, but none of that work has had a change to influence the Jakarta Data spec.

So this is just kinda bad timing. This spec would I guess have made sense some years ago, before this new work started happening, or it might make sense to do something a bit different in a year or two, once we have some more practical experience with the new approaches we're experimenting with right now.

@antoniomacri
Copy link

Hi @Sanne @gavinking, could you give some pointers to the other ideas you were exploring? You mean Panache?

Hibernate introduced support (tech preview) for Jakarta Data earlier this year. Also an article on integrating Jakarta Data has been publicized on Quarkus July newsletter. Something changed from your perspective?

@codespearhead
Copy link

codespearhead commented Aug 29, 2024

it's now available in Hibernate 6.6, which is the Hibernate version used since Quarkus 3.14.0 as per #41359 :

Hibernate 6.6 includes a complete implementation of the Jakarta Data 1.0 Release. As discussed here, our implementation:

  • is based on compile-time code generation via an annotation processor, enabling unprecedented compile-time type safety, and
  • is backed by Hibernate’s StatelessSession, which has been enhanced especially to meet the needs of Jakarta Data.

Hibernate 6.6 is certified as a compatible implementation.

@pipinet
Copy link

pipinet commented Oct 13, 2024

Micronaut data has also been implemented according to the Jakarta data standard。
https://micronaut-projects.github.io/micronaut-data/latest/guide/

@gavinking
Copy link

Hibernate introduced support (tech preview) for Jakarta Data earlier this year. Also an article on integrating Jakarta Data has been publicized on Quarkus July newsletter. Something changed from your perspective?

@antoniomacri Well, yes, we completely rewrote the Jakarta Data spec.

If you're interested, you can learn about the new approach by watching my talk here:

https://www.youtube.com/watch?v=X9GplCb5SWY&t=67s

@pipinet
Copy link

pipinet commented Oct 26, 2024

@gavinking Is there an example of integration between quarkus and hibernate repository?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/persistence OBSOLETE, DO NOT USE kind/enhancement New feature or request triage/wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

7 participants