#2 Java 11 (>= 9), Tomcat 9 (>= 8), the new world order

[Raimund 'Raimi' Jacob]

Hello World! Is anyone besides me still using this?

Background: My application handles email and and "sometimes" the charset "unicode-1-1-utf-7" appears - or appeared, I don't know. It was very rare and it might have gone away completely by now.

Just for my personal record, the situation is explained here: https://github.com/eclipse-ee4j/javamail/issues/269

JavaMail recognizes that one might need this charset if it appears in some mail body.
They also refer to the "regular" SPI loading mechanism.

The JDK people themselfes do not want to add this charset, pointing back to JavaMail: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4304013

Everyone ignores that in a web application context there is no "regular" SPI loading mechanism. There used to be one: Throw jutf7.jar into tomcat/endorsed/

But since Java 9 this does not work any longer.

java -Djava.endorsed.dirs=/tmp -help
-Djava.endorsed.dirs=/tmp is not supported. Endorsed standards and standalone APIs
in modular form will be supported via the concept of upgradeable modules.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

The real question is: Where to actually place this jar file so that it can still provide a new charset.