Does JVM variable java.library.path make sense from native code?

Question

Hello all,
Well, everybody loads native library from the Java side by calling System.loadLibrary("myNative").
But what if, for example, myNative.dll loads another two libraries itself?
Suppose, when I call java method "initMyNative", it in turn call native function Java_initMyNative(...). That Java_initMyNative(...) wants to load two native libraries and make: HINSTANCE lib01 = LoadLibrary("auxlib01.dll");  // LoadLibrary from capital, it's Win function!
HINSTANCE lib02 = LoadLibrary("auxlib02.dll");  // LoadLibrary from capital, it's Win function!As specified, native LoadLibrary call will look for auxlib01.dll and auxlib02.dll in catalogs which are enumerated in system variable PATH, current catalog.
Does java.library.path make any sense on order of such search?
If not, is there any way of flexible configuring of the catalog in which to look auxlib01.dll and auxlib02.dll for?
I see some ways:
* changing system variable PATH - not flexible
* passing content of java.library.path into native code, parsing it and looking for auxlib01.dll and auxlib02.dll in each catalog listed in java.library.path - too heavy
I hope there is more smart way to do that.
Thanks, Alex

Answer 1

Thank you Shane for your reply. I actually didnt have to create 2 jar files, one for Java files and one for the dll file. I got an idea from your post and referenced the same jar file twice by saying:
<j2se version="1.2+" />
<jar href="HelloWorld.jar"/>
<nativelib href="HelloWorld.jar"></nativelib>
and by saying that the jnlp file started working from the browser.
Again, thanks a lot for your replies.
Thanks
Nick