I had recently completed the switch to java 11 Here are my 2c.
There are two jakarta packages activation and activation-api CXF brings by default (via maven) the activation-api. Although the server side this is ok (I think) I have had big problems on the client side. While I was able to compile the application, I had the application failing at runtime due to class not found errors. I think aegis was trying to initialize DataFactory and then was crashing on non existent LogSupport. So I removed activation-api and manually added activation which has the api classes plus some more such as LogSupport. See https://github.com/eclipse-ee4j/jaf/issues/18 for insight. This looks like a layering violation but hey that's life. Note that was true even before jakarta, The complexity of mysq application may also be responsible for this and CXF may have nothing to do with it. Hope that helps On 6/6/19 11:23 AM, Nicola Buso wrote:
Hi everyone, in our application we started looking at updating to OpenJDK 11 (from a Fedora distro for now) --- Apache Maven 3.5.4 (Red Hat 3.5.4-5) Java version: 11.0.3, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.3.7-5.fc30.x86_64 --- I'm compiling against CXF 3.3.2 and getting the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler- plugin:3.8.1:compile (default-compile) on project ebinocle-web: Compilation failure [ERROR] module not found: java.activation If I 'require' java.activation in my java module I will get in trouble because all other dependencies are using jakarta.activation as a requirement. What is the plan for CXF? are you going to move to jakarta.activation or do you have different suggestions? Nicola
-- __________________________________ Vassilis Virvilis Ph.D. Head of IT Biovista Inc.
