You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Richard Zowalla <rz...@apache.org> on 2025/09/26 08:29:25 UTC
[DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
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
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Evaldo Junior <ev...@gmail.com>.
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 <
daniel.dias.analistati@gmail.com> 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 <ex...@gmail.com> 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 <ev...@gmail.com>
> > 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 <
> > > andraschko.thomas@gmail.com> escreveu:
> > >
> > > > +1 for hibernate + hibernate for Jakarta data
> > > >
> > > > Daniel Dias Dos Santos <da...@gmail.com> 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 <rz...@apache.org>
> 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 | exabrial@gmail.com
> > 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.
> >
>
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Daniel Dias Dos Santos <da...@gmail.com>.
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 <ex...@gmail.com> 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 <ev...@gmail.com>
> 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 <
> > andraschko.thomas@gmail.com> escreveu:
> >
> > > +1 for hibernate + hibernate for Jakarta data
> > >
> > > Daniel Dias Dos Santos <da...@gmail.com> 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 <rz...@apache.org> 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 | exabrial@gmail.com
> 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.
>
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by "Jonathan S. Fisher" <ex...@gmail.com>.
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 <ev...@gmail.com>
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 <
> andraschko.thomas@gmail.com> escreveu:
>
> > +1 for hibernate + hibernate for Jakarta data
> >
> > Daniel Dias Dos Santos <da...@gmail.com> 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 <rz...@apache.org> 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 | exabrial@gmail.com
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.
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Evaldo Junior <ev...@gmail.com>.
+ 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 <
andraschko.thomas@gmail.com> escreveu:
> +1 for hibernate + hibernate for Jakarta data
>
> Daniel Dias Dos Santos <da...@gmail.com> 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 <rz...@apache.org> 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
> >
>
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Thomas Andraschko <an...@gmail.com>.
+1 for hibernate + hibernate for Jakarta data
Daniel Dias Dos Santos <da...@gmail.com> 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 <rz...@apache.org> 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
>
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Daniel Dias Dos Santos <da...@gmail.com>.
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 <rz...@apache.org> 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
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Richard Zowalla <rz...@apache.org>.
Thanks for your feedback & thoughts.
The licenses for Hibernate 7 are compliant to our regulations at ASF level; I did a license scan via Maven for 7.1.4.Final.
The results can be found here: [1]
Next, these are valid questions. I have raised them with the OpenJPA community here: [2].
I think they are currently working on JPA 3.2 but aren’t complete yet. I hope, that they will join our discussion and shed some light into that matter.
If we stay with OpenJPA, we would need to discuss how we want to handle Jakarta Data for which we don’t have an implementation at the ASF at the moment.
Start a new project under the ASF EE umbrella? Integrate that into OpenJPA (as Hibernate does)?
I think our main problem at the ASF EE umbrella is the lack of resources, which manifests in many EE related projects as it’s the same small community of people maintaining most of the stack.
Gruß
Richard
[1] https://gist.github.com/rzo1/0bb5ca1921334f422db663b531fe15b4
[2] https://lists.apache.org/thread/sst7x0xsxdfwbfdmv6llmk09zsrly4l4
> Am 16.10.2025 um 11:53 schrieb Jonathan Gallimore <jo...@gmail.com>:
>
> My immediate question would be - Hibernate has some dependencies. I might
> be looking at an out-of-date version, but that could include jboss-logging,
> jandex and others. What's the license on those? At a quick glance, it
> -looks- ok, but I think its worth enumerating what would actually change in
> the artifacts we distribute to make sure we're ok from a licensing
> perspective.
>
> From the perspective of moving away from OpenJPA, I'd be interested in some
> data, and looking at it with an OpenJPA centered view:
>
> * I assume the change is motivated because OpenJPA is behind other
> implementations from a spec compliance perspective. How big is the gap?
> Should we run the TCK and have a look? (I'm hoping to get some time to do
> TCK work shortly, so might be a good opportunity for me to look)
> * Lack of resources - if we know what's needed, could we find the
> time/people?
> * What's OpenJPA's own view on the project status? It looks like there's
> some activity, a release within the last 12 months, and a new committer
> within the last 6 months.
> https://whimsy.apache.org/board/minutes/OpenJPA.html
>
> OpenJPA has been the default persistence provider since forever (or at
> least for whole time I've been involved with TomEE, which is closing in 20
> years now). If TomEE decides not to use OpenJPA, how does that decision
> impact OpenJPA?
> I'm definitely getting old, but I remember presenting TomEE for the first
> time at JAX London in 2011 with David Blevins. It was the All Apache stack,
> where Tomcat is top dog. Here's the slides:
> https://tomee.apache.org/presentations/2011_JavaOne_Apache_TomEE_Java_EE_6_Web_Profile.pdf
> - you can probably find the video on YouTube. Having different
> implementations of the specs gives a bit of diversity in the Jakarta EE
> world. All the app servers could theoretically use the reference
> implementations of everything, but I think that potentially leaves little
> to distinguish them, and reduces innovation opportunity. David can no doubt
> tell stories of functionality that is now part of the spec, but started as
> an experiment in OpenEJB. We've seen a move away from the Geronimo
> MicroProfile implementations to the reference implementation (SmallRye).
> Similar story there - the implementation fell behind, and not enough people
> to fill the gap.
>
> If the TomEE community decided to move to Hibernate and away from OpenJPA,
> I would understand. But I'd be sad about it. It would feel like the 'All
> Apache stack" is now the 'A bit of Apache stack". 20 years ago, I'd have
> been up for some all-night hacking on OpenJPA - unfortunately, personal
> circumstances make that difficult now. I can try and get some $work time on
> it. I'm willing to try and help out on OpenJPA, but I don't know how big
> the task is at the moment.
>
> Jon
>
> On Wed, Oct 15, 2025 at 1:15 PM Richard Zowalla <rz...@apache.org> wrote:
>
>> Hi,
>>
>> I would love to hear some additional feedback (also from within the TomEE
>> PMC)
>>
>> Any thoughts on JPA in TomEE @ Mark, Markus, David, JL or Jon?
>>
>> Gruß
>> Richard
>>
>> On 2025/09/26 08:29:25 Richard Zowalla 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
>>
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Jonathan Gallimore <jo...@gmail.com>.
My immediate question would be - Hibernate has some dependencies. I might
be looking at an out-of-date version, but that could include jboss-logging,
jandex and others. What's the license on those? At a quick glance, it
-looks- ok, but I think its worth enumerating what would actually change in
the artifacts we distribute to make sure we're ok from a licensing
perspective.
From the perspective of moving away from OpenJPA, I'd be interested in some
data, and looking at it with an OpenJPA centered view:
* I assume the change is motivated because OpenJPA is behind other
implementations from a spec compliance perspective. How big is the gap?
Should we run the TCK and have a look? (I'm hoping to get some time to do
TCK work shortly, so might be a good opportunity for me to look)
* Lack of resources - if we know what's needed, could we find the
time/people?
* What's OpenJPA's own view on the project status? It looks like there's
some activity, a release within the last 12 months, and a new committer
within the last 6 months.
https://whimsy.apache.org/board/minutes/OpenJPA.html
OpenJPA has been the default persistence provider since forever (or at
least for whole time I've been involved with TomEE, which is closing in 20
years now). If TomEE decides not to use OpenJPA, how does that decision
impact OpenJPA?
I'm definitely getting old, but I remember presenting TomEE for the first
time at JAX London in 2011 with David Blevins. It was the All Apache stack,
where Tomcat is top dog. Here's the slides:
https://tomee.apache.org/presentations/2011_JavaOne_Apache_TomEE_Java_EE_6_Web_Profile.pdf
- you can probably find the video on YouTube. Having different
implementations of the specs gives a bit of diversity in the Jakarta EE
world. All the app servers could theoretically use the reference
implementations of everything, but I think that potentially leaves little
to distinguish them, and reduces innovation opportunity. David can no doubt
tell stories of functionality that is now part of the spec, but started as
an experiment in OpenEJB. We've seen a move away from the Geronimo
MicroProfile implementations to the reference implementation (SmallRye).
Similar story there - the implementation fell behind, and not enough people
to fill the gap.
If the TomEE community decided to move to Hibernate and away from OpenJPA,
I would understand. But I'd be sad about it. It would feel like the 'All
Apache stack" is now the 'A bit of Apache stack". 20 years ago, I'd have
been up for some all-night hacking on OpenJPA - unfortunately, personal
circumstances make that difficult now. I can try and get some $work time on
it. I'm willing to try and help out on OpenJPA, but I don't know how big
the task is at the moment.
Jon
On Wed, Oct 15, 2025 at 1:15 PM Richard Zowalla <rz...@apache.org> wrote:
> Hi,
>
> I would love to hear some additional feedback (also from within the TomEE
> PMC)
>
> Any thoughts on JPA in TomEE @ Mark, Markus, David, JL or Jon?
>
> Gruß
> Richard
>
> On 2025/09/26 08:29:25 Richard Zowalla 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
>
Re: [DISCUSS] Future of OpenJPA in TomEE 11 / EE 11
Posted by Richard Zowalla <rz...@apache.org>.
Hi,
I would love to hear some additional feedback (also from within the TomEE PMC)
Any thoughts on JPA in TomEE @ Mark, Markus, David, JL or Jon?
Gruß
Richard
On 2025/09/26 08:29:25 Richard Zowalla 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