jna.library.path is provided for when you know what the path is.
Since web start requires native libraries be at the root of the
classpath, you should be able to ask the class loader for the
resource by name, which should give you a URL on the filesystem where
webstart is cacheing the library. If it's not on the FS, you can
copy it someplace where you can use it.
Once you've got that you can either set jna.library.path or
explicitly pass the path of the library to Native.loadLibrary.
On Sep 5, 2007, at 12:56 PM, robert engels wrote:
Is there anyway to deploy an application that uses a custom DLL and
have it work when accessing via JNA?
That is, we don't want to manually copy the dependent dll into the
windows path.
We would like to deploy the dependent jar similar to how other
native jars are deployed with webstart (in a native.jar).
None of the examples use a jar other than the system ones (which
are already available in the path).