http://community.borland.com/article/0,1410,20951,00.html

But I don't understand the part about "java.library.path".

The end result, the application compiles, but fails when it tries to run (error output below).

  java.lang.UnsatisfiedLinkError: no J3D in java.library.path
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)

Is doing this restricted in JBuilder Foundation?
----------
This is not restricted in Foundation.

Open your project properties, and in the VM Parameters field, add this:

  -Djava.library.path=c:\path\to\java3d's-dlls\here

Perhaps something like:

  -Djava.library.path=c:\jdk1.2.2\lib\windows

Or whatever the path actually is for that package. I don't use it so I can't look it up for you.

This is necessary because the dll files containing the native code portions of the Java 3D API aren't in a directory windows will search when the JVM asks the OS to load the J3D.dll file. The java.library.path variable tells the JVM to ask windows to look in the specified directory as well.

However, the behavior of this variable seems to be platform-dependent. On Linux this value is appended to the system default search path for libraries, but on Windows it seems to OVERRIDE the system default.

You may need to list additional windows directories in that java.library.path as well, separated by your platform's standard path separator. (I think it's a ; on windows, but it's : on unix.)

2001-Feb-17 5:22pm gyles19@visi.com