diff options
| author | Christof Rabensteiner <christof.rabensteiner@iaik.tugraz.at> | 2019-08-22 10:05:03 +0200 |
|---|---|---|
| committer | Christof Rabensteiner <christof.rabensteiner@iaik.tugraz.at> | 2019-08-23 15:17:14 +0200 |
| commit | e6e0950a506d814415d8036e68e54d2034b6d3e7 (patch) | |
| tree | 8dc0f1c57f063f639ad884a03f951ea9a9f2fb7c /src/test/resources/config/ssl/server/server.localhost.cert.pem | |
| parent | 763724b04d25d07fce5559c1d7a6c12badab937c (diff) | |
| download | moa-zs-e6e0950a506d814415d8036e68e54d2034b6d3e7.tar.gz moa-zs-e6e0950a506d814415d8036e68e54d2034b6d3e7.tar.bz2 moa-zs-e6e0950a506d814415d8036e68e54d2034b6d3e7.zip | |
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)
Diffstat (limited to 'src/test/resources/config/ssl/server/server.localhost.cert.pem')
0 files changed, 0 insertions, 0 deletions