Java 11 status

Hey TomEE lovers, I would like to push the Java 11 support forward. I tried to gather information here and there. Here is a status with my view. Please, lemme know if you have further updates or any additional information. XBean: ready and released OWB: ready and released TomEE itself (OpenEJB a

Re: Java 11 status

Hi JL Openjpa needs xbean upgrade but should be quick. Cxf stack needs some jaxb upgrades from memory. After the stack "supports" java11 as "run it" but think no spec in EE is java >= 9 compatible (modules, spi etc). Should be enough for tomee that said. Le jeu. 8 nov. 2018 20:27, Jean-Louis Mo

Re: Java 11 status

About MyFaces: we are not aware of any issue, but i didn't test it explicitly in theory there could be problem when scanning the classpath and reading the classes but AFAIK this part is completely replaced by TomEE via MyFaces SPI (AnnotationProvider) Am Do., 8. Nov. 2018 um 20:27 Uhr schrieb Jean

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 org.apache.openejb.javaagent.Agent.checkInitialization(Agent.java:10

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 com.sun.xml.bind.v2.

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

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

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 least

Re: Java 11 status

We also need to wait for commons-pool and commons-dbcp. I fixed a deadlock in the pool.Only after that I'll be able to release OpenJPA. LieGrue,strub On Friday, 9 November 2018, 21:02:13 CET, Mark Struberg wrote: Right now I do a lot of OpenJPA hacking. One of the tasks is to also sup

Re: Java 11 status

Shouldnt be the case Mark since openjpa is not bound to a pool - except in tests - and tomee default pool is not dbcp2 but tomcat-jdbc. So it is not a requirement but more a nice to have IMHO. Also not a regression since last release so not a blocker ;). Le sam. 10 nov. 2018 21:02, Mark Struberg

Re: Java 11 status

Agreed. Probably we don't need to wait for it. At least we could do a M2 which is Java 11 ready. Le sam. 10 nov. 2018 à 21:49, Romain Manni-Bucau a écrit : > Shouldnt be the case Mark since openjpa is not bound to a pool - except in > tests - and tomee default pool is not dbcp2 but tomcat-jdbc

Re: Java 11 status

The problem is that the unit tests in OpenJPA do not pass with the old pool. So for getting OpenJPA-3.0.1 we need commons-pool. OpenJPA-3.0.0 still uses xbean-asm6. Means different package.We would need to package both xbean-asm6 and xbean-asm7 if we want to ship TomEE with OpenJPA-3.0.0. LieG

Re: Java 11 status

The unit tests point is likely easy to solve either using another pool or just not using a pool for tests. Also the bug you fixed happens under some particular case we can workaround using bigger pools I think. Asm upgrade is really a few seds (I can help end of next week - thursday I think - if ne

Re: Java 11 status

If you are willing to help me, I can do it tomorrow Le dim. 11 nov. 2018 à 12:21, Romain Manni-Bucau a écrit : > The unit tests point is likely easy to solve either using another pool or > just not using a pool for tests. Also the bug you fixed happens under some > particular case we can workaro

Re: Java 11 status

@Jean-Louis should i create jira tickets for my 2 issues in this thread? Virenfrei. www.avast.com

Re: Java 11 status

Yes please. Le dim. 11 nov. 2018 à 23:15, Thomas Andraschko a écrit : > @Jean-Louis > should i create jira tickets for my 2 issues in this thread? > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > Virenfrei. > www.avast.com

Re: Java 11 status

done: https://issues.apache.org/jira/browse/TOMEE-2270 https://issues.apache.org/jira/browse/TOMEE-2271 Am So., 11. Nov. 2018 um 23:28 Uhr schrieb Jean-Louis Monteiro < jlmonte...@tomitribe.com>: > Yes please. > > > Le dim. 11 nov. 2018 à 23:15, Thomas Andraschko < > andraschko.tho...@gmail.com>

Re: Java 11 status

Ok, created https://issues.apache.org/jira/browse/TOMEE-2272 for XBean upgrade Here is the commit https://github.com/apache/tomee/commit/14919e15178e6f45254da74d3574dcb9312c54a1 Build locally passes. Waiting for buildbot now -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomi

Re: Java 11 status

Ok, working on ticket TOMEE-2273 Thomas created. I'll be switching to OWB 2.0.8 that just got released. @Thomas, should I be looking at TOMEE-2270 and TOMEE-2271? -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com

Re: Java 11 status

Yes, please :) Am Di., 13. Nov. 2018, 09:52 hat Jean-Louis Monteiro < jlmonte...@tomitribe.com> geschrieben: > Ok, working on ticket TOMEE-2273 > Thomas created. > I'll be switching to OWB 2.0.8 that just got released. > > @Thomas, should I be lo