>> Locating a native library loaded by a Java jar is typically done >> using relative path entries in the jar manifest Class-Path. >> Resolving a relative path relative to a symlink can obviously have >> different results, depending on whether or not the symlink is resolved. > For Java there seems to be no problem resolving symlinks. I placed my > main jar in <OO Installation>/basis-link/program/ and did put symlinks > and other needed jars into a newly createed <OO > Installation>/basis-link/program/lib folder. Resolving those symlinks > was no problem for Java as I could see in -verbose mode. All > classes/methods were properply loaded, except those JNI methods. I > don't know why it is like that and if that is needed or a missing > feature from classloaders/infrastructure. just a wild guess: if you are relying on the operating system to locate the libs, then you may be hit by "ldconfig"'s not processing symlinked files.
---rony --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
