From e6e0950a506d814415d8036e68e54d2034b6d3e7 Mon Sep 17 00:00:00 2001 From: Christof Rabensteiner Date: Thu, 22 Aug 2019 10:05:03 +0200 Subject: Fix: JAXB + Java >= 9 Class Loader Bug & Ensure Tomcat Deployment - Problem: Jaxb + JAVA >= 9 Runtime + Tomcat = ClassNotFoundException: ContextFactory. Reason: Apparently, jaxb uses the "wrong" classloader (the system classloader via the thread classloader) and this classloader does not know about jaxb api's and implementations at runtime since oracle decided to move jaxb* out of JRE. Solution: create a new thread, override the thread's "thread" classloader with the "class" classloader and do all jaxb interactions in that thread. See: https://sjhannah.com/blog/2018/11/21/jaxb-hell-on-jdk-9/ - Move "run jaxb interactions in own thread with class class loader" code into own component (JaxbClassNotFoundFix, runInTheadWithClassClassLoader) and wrap ClientFactory and Marshaller code into the "runInTheadWithClassClassLoader". - Ensure that app can be deployed in a Tomcat container (by following this guide: https://www.baeldung.com/spring-boot-war-tomcat-deploy) --- pom.xml | 38 +++++++++++++++++++------------------- 1 file changed, 19 insertions(+), 19 deletions(-) (limited to 'pom.xml') diff --git a/pom.xml b/pom.xml index 62a5bdf..a8191bf 100644 --- a/pom.xml +++ b/pom.xml @@ -92,11 +92,11 @@ test - org.springframework.boot - spring-boot-starter-tomcat + org.springframework.boot + spring-boot-starter-tomcat ${springboot.version} - provided - + provided + org.apache.cxf @@ -143,23 +143,23 @@ ${jwsapi.version} - + + at.gv.egiz.eaaf + eaaf_module_moa-sig + ${eaaf-components.version} + + at.gv.egiz.eaaf - eaaf_module_moa-sig + eaaf-core ${eaaf-components.version} - - - at.gv.egiz.eaaf - eaaf-core - ${eaaf-components.version} - - - - org.awaitility - awaitility - 3.1.6 - test - + + + + org.awaitility + awaitility + 3.1.6 + test + moa-zs -- cgit v1.2.3