A custom class uses loadLibrary() to load a DLL or other library and the installer doesn't start or crashes.


If you have a custom class which loads a library, Sun used to suggest that you use loadLibrary() and allow the jvm to find the file. Now Sun appears to be advocating that you include the full path so DeNova is suggesting that you use load() instead of loadLibrary().

You can find the path to the JVM the installer is using by calling System.getProperty("java.home") and prepend this to the file you want to load.

JExpress always uses the JVM that it uses to configure your app to use so if you're shipping a special version of the JVM bundle which includes special libraries, then you can force the installer to install the shipped JVM so you'll know that you have access to all the extra files during installation as well as after it.

Applies to
loadlibrary, dll

All information is provided "as is", without warranty of any kind, and subject to change. DeNova uses its best efforts to provide complete and accurate information. DeNova disclaims all warranties, either explicit or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall DeNova or its suppliers be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special damages, even if DeNova or its suppliers have been advised of the possibility of such damages.