(by replacing the eclipselink jar in the tomee lib directory, as you described)
On Sat, Sep 21, 2019 at 8:09 PM Jonathan S. Fisher <[email protected]> wrote: > We regularly run TomEE 7.0.x with upgraded Eclipselink 2.7.4 and use the > latest JPA features with no issues :) Make sure both your orm.xml and > persistence.xml schema point to the correct XSD or you'll have some issues. > > On Sat, Sep 21, 2019 at 3:34 PM Vano Beridze <[email protected]> wrote: > >> If I replace a jar file in the lib folder, should it work? >> >> On Sun, Sep 22, 2019 at 12:28 AM Jean-Louis Monteiro < >> [email protected]> wrote: >> >> > Hi, >> > >> > It actually depends on what you download. By default, TomEE uses >> OpenJPA. >> > The PLUME distribution switches both JPA from OpenJPA to EclipseLink and >> > MyFaces to Mojora for JSF. >> > >> > I think the API embedded in TomEE 8 should be 2.2 or we have an issue we >> > should fix. >> > If that's the case, I don't think there would be any issue upgrading >> > Eclipse Link to compatible version. >> > >> > >> > -- >> > Jean-Louis Monteiro >> > http://twitter.com/jlouismonteiro >> > http://www.tomitribe.com >> > >> > >> > On Sat, Sep 21, 2019 at 12:55 PM Vano Beridze <[email protected]> >> wrote: >> > >> > > Hello, >> > > >> > > I've downloaded tomee 8.0.0 and deployed java ee 8 application. >> > > From what I can see it's handled by EclipseLink 2.6.4 which is Java >> EE 7 >> > > compliant. >> > > >> > > Kind regards, >> > > Vano >> > > >> > >> > > > -- > 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. > -- 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.
