Posted by gouessej on Jan 07, 2018; 6:27pm
URL: https://forum.jogamp.org/Jogl-Jogamp-on-Java-9-tp4038012p4038487.html

If ImageJ installed a JVM with Java3D installed inside it as an extension and if somehow Java Webstart uses this JVM, it won't work. Please look at the whole hard drive. Do you use a virus scanner under Windows? My JOGL example works fine under Microsoft Windows 10, 8, 7, Vista, ... I don't blame Java3D for this but JOGL is not to blame neither (only for the problem under Windows), there is something wrong on your machine. I can retry if you want but I can only use Windows 10. I have no longer access to Windows 7.

Was there anything in the imagej folder?

Thank you. Only the first link was broken. I've just fixed it. If you choose JNDT, you'll be able to use any JRE, you'll have full control on what is provided, you won't depend on what is installed on the system except when it looks for things in the path, you'll be able to disable the automated native library loading to eliminate some problems with some virus scanners. The only remaining problem will come from very paranoid virus scanners that go on treating GlueGen as a virus... and there is a real bug to fix in JOGL when releasing the context under OS X with Java 1.9.

Actually, I advise you to make my example work without Java Webstart and then to make it work with Java Webstart in order to determine whether it's the culprit. I understand your position as I used Java Webstart for years but there is not much I can do. You have shown several bugs on 2 operating systems here, we should solve them one by one but I cannot guarantee that it will work with Webstart. Maybe some native libraries are no longer provided in Java 1.9 or maybe they aren't loaded when using Webstart, that's why it would be interesting to know whether it works without Webstart.