I worked with Eclipse Link a few years ago. The reason I chose it was because of its caching, and it would have advantages over Hibernate for complex queries. But Hibernate is the market pattern and the JPA specification. The JPA specification was based on it. And for those who don't know the Hibernate, it's easier to learn than Hibernate, with a shorter learning curve.
Evaldo Junior Em sex, 26 de set de 2025 13:48, Daniel Dias Dos Santos < [email protected]> escreveu: > I don’t know much about EclipseLink, I only worked with it once on > WebLogic. > > But does it already have the latest JPA updates and integration with > Jakarta Data? > > I’m a bit out of touch with the recent evolutions of the Jakarta EE > platform. > > > On Fri, Sep 26, 2025, 11:14 Jonathan S. Fisher <[email protected]> wrote: > > > My vote would actually be EclipseLink, not Hibernate :) I've used both > and > > greatly prefer it at scale, especially in how it performs with its cache. > > However, as long as there continues to be a TomEE distribution with > > Eclipselink in it, tis a mute point what the default is IMHO. > > > > On Fri, Sep 26, 2025 at 8:36 AM Evaldo Junior <[email protected]> > > wrote: > > > > > + 1 vote to use Hibernate insted of Open Jpa. > > > I have never used OpenJpa. > > > I have been using Hibernate since 2.006. > > > > > > > > > Evaldo Junior > > > > > > Em sex, 26 de set de 2025 10:18, Thomas Andraschko < > > > [email protected]> escreveu: > > > > > > > +1 for hibernate + hibernate for Jakarta data > > > > > > > > Daniel Dias Dos Santos <[email protected]> schrieb am > > > Fr., > > > > 26. Sept. 2025, 14:34: > > > > > > > > > Hello, > > > > > > > > > > I vote +1 to make Hibernate the default in TomEE. > > > > > > > > > > Honestly, I have never used OpenJPA. > > > > > > > > > > And most developers use Hibernate. > > > > > > > > > > Since it is already under the Apache license, I believe it would > be a > > > > huge > > > > > gain for the project, as it has a strong community around it and is > > > > already > > > > > implementing Jakarta Data. > > > > > > > > > > > > > > > > > > > > On Fri, Sep 26, 2025, 05:29 Richard Zowalla <[email protected]> > wrote: > > > > > > > > > > > Hi all, > > > > > > > > > > > > I’d like to start a discussion about the future of OpenJPA in > > TomEE, > > > > > > specifically whether it’s time to consider replacing it with > > > Hibernate. > > > > > > > > > > > > Hibernate 7 is now ASLv2 licensed, fully implements the latest > spec > > > > > > features, and already supports Jakarta Data for EE 11. This puts > it > > > in > > > > a > > > > > > strong position to meet our needs moving forward, especially as > we > > > look > > > > > > toward TomEE 11. > > > > > > > > > > > > By contrast, OpenJPA has struggled to keep up, and realistically > we > > > > don’t > > > > > > appear to have enough development resources to build and maintain > > an > > > > > > ASF-only implementation of Jakarta Data. In fact, we made a > similar > > > > > > decision when we gave up the ASF-only spec implementations some > > time > > > > ago. > > > > > > > > > > > > Of course, anyone who prefers to stay with OpenJPA can still swap > > it > > > > in, > > > > > > but from my perspective, I believe we should seriously consider > > > whether > > > > > > Hibernate should become the default going forward. > > > > > > > > > > > > I’d like to hear your thoughts, both on the practical > implications > > > for > > > > > > TomEE and the overall direction we should take. > > > > > > > > > > > > Gruß > > > > > > > > > > > > Richard > > > > > > > > > > > > > > > > > > -- > > Jonathan | [email protected] > > Pessimists, see a jar as half empty. Optimists, in contrast, see it as > half > > full. > > Engineers, of course, understand the glass is twice as big as it needs to > > be. > > >
