Re: Java 11 status

Right now I do a lot of OpenJPA hacking. One of the tasks is to also support xbean-asm7. That should go into openjpa-3.0.1. What is the timeframe we want to target? LieGrue, strub > Am 09.11.2018 um 14:18 schrieb Romain Manni-Bucau : > > I don't have the list handy but tomee will need at

Re: Java 11 status

I don't have the list handy but tomee will need at least some --add-opens etc to run on java11 (you can add it in setenv.sh) - likely for unsafe and the agent. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: Java 11 status

(e.g. Tomcat and DeltaSpike still uses the old namespace it's in web/beans.xml) Am Fr., 9. Nov. 2018 um 13:35 Uhr schrieb Thomas Andraschko < andraschko.tho...@gmail.com>: > Also looks like XML unmarshalling is broken: > > Caused by: javax.xml.bind.UnmarshalException: unerwartetes Element (URI:"

Re: Java 11 status

Also looks like XML unmarshalling is broken: Caused by: javax.xml.bind.UnmarshalException: unerwartetes Element (URI:" http://java.sun.com/xml/ns/javaee;, lokal:"interceptors"). Erwartete Elemente sind <{}trim>,<{}decorators>,<{}scan>,<{}alternatives>,<{}interceptors> at

Re: Java 11 status

@Jean-Louis Are you saying that TomEE8 M1 itself is not compatbile with Java11? Currently trying to run my application with tomee-maven-embedded and it fails: java.lang.IllegalStateException: Unable to initialize agent at