Date: Fri, 29 Mar 2024 06:17:12 +0000 (UTC) Message-ID: <874561084.10911.1711693032538@911f0a1bad02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10910_1130354863.1711693032538" ------=_Part_10910_1130354863.1711693032538 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Servoy supports through the admin page Java9 from 815/82 on. We = have then the configuration option to choose java9 as minimum or maximum.= p>
For bootstrap.jnlp you can add the <j2se> tag yourself but the ver= sion is not 1.9 (like 1.7/1.8 before) but now just 9, so without the 1. bef= ore it.
To run the smart client some vm args must be given to so that the Window= s Look and Feel will work (and possible others should be added if more exce= ptions are seen as shown below:
The exception that the java console log will give under windows is somet= hing like:
java.lang.IllegalAccessException: class com.servoy.j2db.LAFManager canno= t access class com.sun.java.swing.plaf.windows.WindowsLookAndFeel (in modul= e java.desktop) because module java.desktop does not export com.sun.java.sw= ing.plaf.windows to unnamed module @6c6fdd7c
For this we need to add on the admin page (vm args section of the smartc= lient) or the bootstrap.jnlp file the vm args of the <j2se> tag:
--add-exports=3Djava.desktop/com.sun.java.swing.plaf.windows=3DALL= -UNNAMED
--add-exports=3Djava.desktop/sun.java2d=3DALL-UNNAMED
So it could be that more IllegalAccessException like that are showin wit= h
class X cannot access class <some.package>.Class in module <som= e.module>
that means we need to add another --add-exports in this syntax:
--add-exports=3D<some.module>/<some.package>=3DALL-UNNAMED= p>
See http://openjdk.java.net/jeps/261 for more i= nfo
Also Java9 and the developer is here https:= //wiki.servoy.com/display/DOCS/Java+9+support+for+the+developer
The other problem is the bug Oracle did introduce in Java 9 (as a regres= sion from Java 8) that they until now don't plan to fix for Java 9 (but onl= y Java 10). We don't have an workaround for that because we heavily depend = on this to resolve the media:/// urls (media from the solution or from the = database through the blobloader syntax)
https://bugs.openjdk.java.net/browse/JDK-8178= 799
So all kinds of media:/// urls directly set on the components are there = images or inside <html> markup that is shown on labels are not resolv= ing to the right image.
For Java 11 there is a bigger problem because there is no JRE anymore th= at integrates into the system that also supplies webstart.
So the only way to start it there is to use the bootst= rapper in standalone mode and you need to install java and setup = the paths correctly so you can run java -jar bootstrap.jar