Posted by Larry Tesler on Jun 03, 2016; 8:23pm
URL: https://forum.jogamp.org/J3D-JOGL-good-within-Eclipse-but-UnsatisfiedLinkError-as-standalone-tp4036783p4036790.html

EDIT: Reformatted using quote tags to clarify who said what.

Phil,

Larry Tesler wrote

philjord wrote

The easiest thing to do is then delete the java3d jars (including vecmath.jar) from that
folder and re-test.

*** QUESTION: Should I remove the four jars from the Eclipse project's jre\lib\ext and rebuild? ***

I think the answer is "no", a rebuild should not be necessary. But I may be wrong.

Larry Tesler wrote

philjord wrote

 A/ change to Java3D 1.7 where all package names have been altered to not match the
legacy names.

"A" sounds appealing. I will look into it.

I haven't found a download site for Java3D 1.7. What I've read about it is several months old.
Is it something that could ship in a product? Is it in GitHub? Where?

philjord wrote

B/ use something like -Djava.ext.dirs=.\none\ in your start up properties. Though
this this you can't access any jar in > the ext folder and so you'd need to find what you
use (if anything) and move it into your project (a good idea anyway).

Into my BigOldApp project? What's involved in moving (for example) SunJCE into BigOldApp? Just
dragging the jar file from jre\lib\ext to BigOldApp\lib (or BigOldApp\lib\anydir)? Revise the
classpath? Rebuild?

ADDED,EDITED,EDITED: I found a book chapter on line (Java Security, 2d Ed., O'Reilly, May 2000). It uses SunJCE as an example of a library that can live in "ext" ("installed") or elsewhere ("unbundled" with edits to java.policy). The files and directories in the example are somewhat obsolete--or evolved--but perhaps the process hasn't changed, or there's better documentation now?
    http://www.onjava.com/excerpt/java_security_ch1

Larry Tesler wrote

The app uses several things in ext. Why is it a good idea to move them into the
project? One downside: Whenever we release an app update with a different jre bundled,
we'll have to repeat the surgery.

I think the answer to my question is that future Javas from Oracle will not support the current
extension mechanism.

Larry