It is looking for that shared object, plus everything that shared object
links to. You can use ldd (list dynamic dependencies) against any library
or executable to see what resolves and what doesn't. Any time java requires
native libraries, a design called JNI (java native interface) is used. JNI
allows java to load native libraries (your dll/so/a files) so that execution
is performed using the native libraries instead of java class files. The
method 'System.LoadLibrary' is used to load the native libraries. This
method can be called from any class; the name of the class does not
necessarily have to match that of the native library.
You can tell java how to find the native libraries by using either the
LD_LIBRARY_PATH (UNIX) or PATH (win32) or as a value passed to java via the
java.library.path parameter. This (albeit a sloppyg/lazy method) is why
dropping these dll's into the system32 directory addresses java finding the
native libraries.
See http://java.sun.com/docs/books/jni/html/design.html for add'l info on
JNI.
Axton Grams
On Tue, Apr 1, 2008 at 6:30 PM, Nicoll, Alan [EMAIL PROTECTED] wrote:
**
Is the JVM actually looking for libarjni63.so when it posts this error or
is it some other file and is the java.library.path the CLASSPATH? I have
that location and every other one with a .jar on my CLASSPATH but still get
the error. I cannot find anything with that name as a .class in any .jar or
anywhere else in my system.
-Nick
DON'T PANIC -The Book
__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
html___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
