I do like the directly, I think we can even mention OSGi (Apache Karaf and Apache Felix do rely on it).
I also think we should abandon openjpa-all artifact, keep it released for backward compatiibility but it is creating us issues with JPMS and other env so maybe we shouldn't promote it anymore and just promote standard modular dependencies like openjpa-persistence-jdbc and friends - or at least "openjpa" alone cause openjpa-all really brings too much today IMHO. With this small fix I'm +1 for it. Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino <https://javaccino.dev/> founder (Java/.NET service - contact via linkedin) Le lun. 2 nov. 2026 à 14:25, Paulo Araújo via dev <[email protected]> a écrit : > What about something like this? > > > ### > OpenJPA may be used in standalone environments and Jakarta WebProfile and > Jakarta EE servers. > > To use in standalone mode, add openjpa-all artifact to your project. > > To use in WebProfile and JakartaEE servers, please check how to do it > using their documentation: > > > > * link to TomEE main site > > * link to Glassfish main site > > * link to OpenLiberty main site > > * link to Spring main site > > > > When using a server that does not come with OpenJPA pre-loaded, please be > sure to add openjpa and xbean-asm9-shaded artifacts to the environment. > ### > > > Do you think it is agnostic enough? > > Paulo > > > > > > > > > > > De: Romain Manni-Bucau <[email protected]> > Para: <[email protected]> > Cc: "Paulo Araújo"<[email protected]>, "Richard Zowalla"< > [email protected]> > Data: seg., 02 nov. 2026 04:33:10 -0300 > Assunto: Re: Updating site integrations instructions > > > > Hi > > What about dropping them all and just having a page referencing the > server. > For ex I know TomEE doc is totally partial and even outdated on some parts > so think it is better to keep the doc where it belongs too with a strong > linking instead. > > Romain Manni-Bucau > @rmannibucau < https://x.com/rmannibucau > | .NET Blog > < https://dotnetbirdie.github.io/ > | Blog < > https://rmannibucau.github.io/ > | Old > Blog < http://rmannibucau.wordpress.com > | Github > < https://github.com/rmannibucau > | LinkedIn > < https://www.linkedin.com/in/rmannibucau > | Book > < > https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064 > > > Javaccino < https://javaccino.dev/ > founder (Java/.NET service - contact > via > linkedin) > > > Le lun. 2 nov. 2026 à 02:20, Maxim Solodovnik < mailto: > [email protected] > a > écrit : > > > +1 :) > > > > On Mon, 2 Nov 2026 at 02:01, Richard Zowalla via dev > > < mailto:[email protected] > wrote: > > > > > > +1 > > > > > > > Am 01.11.2026 um 17:22 schrieb Paulo Araújo via dev < > > mailto:[email protected] >: > > > > > > > > Hi, guys! > > > > > > > > > > > > > > > > @solomax is working on openjpa-site ( > > https://github.com/apache/openjpa-site ) PR#7 to update it. > > > > > > > > Reviewing the text on "integrations", I've noticed that there are > > really outdated instructions on integrations with Apache TomEE, Apache > > Geronimo, Sun (now Eclipse) Glassfish, Sun (now Oracle) Application > Server > > 9.x, IBM WebSphere AS, JonAS, BEA Weblogic and Spring. > > > > > > > > > > > > > > > > I propose we could keep guides to only four technologies: > > > > > > > > * Apache TomEE > > > > > > > > * Eclipse Glassfish (it is just reflected in Oracle AS) > > > > > > > > * IBM OpenLiberty > > > > > > > > * Spring (if we managed to do that) > > > > > > > > > > > > > > > > What are your thoughts about it? > > > > > > > > Best regards to you all, > > > > > > > > > > > > Paulo. > > > > > > > > > -- > > Best regards, > > Maxim > >
