This is a known issue with Eclipse signed artifacts.
You have to exclude the persistence API jar and replace it with another
one. Would need to check if you can't find it, but when I worked on TCK I
had the same issue.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
Quick google in case it helps
Excluding javax.persistence dependency and adding this one may fix the issue
org.eclipse.persistence
org.eclipse.persistence.jpa
2.7.1
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 1, 2019 at
Thanks for the feedback - I'll take a look at that and get back to you.
Jon
On Fri, Sep 27, 2019 at 5:23 PM Paul Carter-Brown
wrote:
> Hi Jon,
>
> I've tried with 8.0.1-SNAPSHOT and get an error:
>
> INFO: Configuring enterprise application:
>
>
Hi Jon,
I've tried with 8.0.1-SNAPSHOT and get an error:
INFO: Configuring enterprise application:
/home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service
Sep 27, 2019 3:58:30 PM org.apache.openejb.config.ReadDescriptors deploy
SEVERE:
Hi Paul
Using 8.0.1-SNAPSHOT should work already - let me know if it doesn't. There
another pending fix for the standalone server - I was planning to propose a
release once that's in.
Jon
On Fri, Sep 27, 2019 at 10:19 AM Paul Carter-Brown
wrote:
> Hi Jon,
>
> Any chance 2.7.4 can be pushed
Hi Jon,
Any chance 2.7.4 can be pushed into an official TomEE build so that we can
use the tomee maven plugin and get this fix. Right now we can manually
upgrade for a normal deployment but our integration tests that use the
tomee maven plugin use 2.7.3.
Paul
On Wed, Sep 25, 2019 at 10:31 PM
Thanks Jon
Worked a charm.
Paul
On Wed, Sep 25, 2019 at 9:17 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Looks like the update to EclipseLink 2.7.4 I committed this morning fixes
> it. Could you try swapping out the EclipseLink jar in your Plume
> distribution lib directory
Looks like the update to EclipseLink 2.7.4 I committed this morning fixes
it. Could you try swapping out the EclipseLink jar in your Plume
distribution lib directory for 2.7.4 and let us know how you get on?
Hi Jonathan,
Seems like it's related to using PLUME (Eclipselink) where a
persistence.xml is present.
Logs are as attached along with a simple war that fails. If I comment out
the contents of my persistence.xml file then it boots fine (but
EntityManagers are all null).
If I include
The short answer is yes - TomEE 8.0.0 should work fine on Java 11. We
definitely want to know about your issue and dig into it.
Can you provide your boot output? I did just double check with a vanilla
TomEE 8.0.0 Plus and OpenJDK 11 from AdoptOpenJDK on my Mac here - its
booted fine. Output is
10 matches
Mail list logo
