Quarkus: EclipseLink

[sniew]

Description
(Describe the feature here.)

Could you please add support to eclipselink ORM

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mann-ed]

This is a feature i would like as well. I have several Thorntail apps i would like to move over to Quarkus, but i don't want to switch to using hibernate as JPA provider. I could help if had some guidance on implementing this.

[ia3andy]

@maxandersen this one has 4 likes, I don't know about EclipseLink ORM. Would it be an extension? Maybe we should move that one to the Quarkus core repo?

[maxandersen]

yes, this is for quarkus core repo.

[maxandersen]

worth stating here that making hibernate work with graalvm and be superfast to boot up in Quarkus was not a small feat requiring intimidate knowledge about Hibernate. We don't have such knowledge about EclipseLink thus this isn't something we would be able to do without the EclipseLink community/committers driving it.

[Sanne]

I don't think we'll be able to do this: getting Hibernate ORM to work fine was a massive amount of work, and it's not econimically wise to spend the same effort on another project which would essentially provide the same / very similar feature.

Sorry but I'll close this, anyone feel free to do this outside of the Quarkus repository.

Is there any specific reason you need EclipseLink and couldn't just use Hibernate ? If so, please list the details.

[emmanuelbernard]

I am reopening this issue to let everyone vote for interest. And also see if someone is willing to implement an eclipse link extension.
The existing contributors will not spend time on it though for the reasons stated above. This is going to be significant work on both eclipse link and the extension itself.
It will also likely require extra work in how Quarkus handles JPA providers.

I don’t think it needs nor should be in the Quarkus core repo (as was stated above). This would live in its own repo.

[Sanne]

Well ok I'm not against having more comments. But if you agree it doesn't belong in this repository, then we'll need a way to not have such issues get stale here either.

For the record, if anyone wants to try getting EclipseLink to work: my main concern is that you'll have to know its internals very well, and likely contribute some rather invasive patches to the project to get it to work in _native-image_ .

[emmanuelbernard]

Today the quarkus issue is for the whole platform unfortunately. Got to live with that I don't see any obvious way around it that would not make life harder.
Issues don't get stale anymore except when they come from code.quarkus.io for some reason. Also extension-proposal would be naturally excluded from a stale process (or should).

[hosseinmp76]

Is there any specific reason you need EclipseLink and couldn't just use Hibernate? If so, please list the details.

the only reason I see is that EclipseLink has moved to Jakarta ee namespace(it's still beta) but there is no clue on hibernate when it will migrate(its sill on v6 development)

[Sanne]

Is there any specific reason you need EclipseLink and couldn't just use Hibernate? If so, please list the details.

the only reason I see is that EclipseLink has moved to Jakarta ee namespace(it's still beta) but there is no clue on hibernate when it will migrate(its sill on v6 development)

Ironically, we haven't updated Hibernate to Jakarta EE because it wouldn't work in Quarkus unless all other technologies to integrate with also switched at the same time (to avoid a mess).

We could explore doing this, but your comment is the first I've seen asking for it.

[sniew]

For legacy reason i use eclipselink instead of hibernate for the support of dynamic entities.