An user reported issues running jSAVF with messages related to the loading of the application config. It seems the way the Java XML properties files are loaded changed in one of the recent Java releases, and as a result jSAVF was no longer able to load its configuration or start.
After doing a bit of digging, the Java bug that was fixed and backported to the LTS JREs was probably the following: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8214820.
Apparently the Properties.loadFromXml() method now rejects XML properties with an embedded DTD such as :
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE properties [ <!ELEMENT properties (comment?, entry*)> <!ATTLIST properties version CDATA #FIXED "1.0"> <!ELEMENT comment (#PCDATA)> <!ELEMENT entry (#PCDATA)> <!ATTLIST entry key CDATA #REQUIRED> ]> <properties> ...and will now only accept documents such as :
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> <properties> ...despite the two DTDs describing the exact same constraints, and the elements actually respecting them.
So I've converted the config back to the old properties format is less likely to suffer such regressions in the future, and also because it didn't really need to be XML.
I've also taken this opportunity to update the OpenJDK JRE which is bundled in the Windows installer (v11.0.7+10), the NSIS installer itself (v3.0.5), plus some other dependencies (slf4j, some build tools...).
If you encounter any issue with this version don't hesitate to reach out to me.