and at the runtime it does the right thing to load it.
Because of this, you normally just have to bundle
com4j.jar with your application.
The only downside of this convenient approach is a sligh runtime performance hit.
Alternatively, you can either:
com4j*.dllin the same directory as
- Set the system property
java.library.pathto include the directory where
com4j*.dllresides. This needs to be done when you launch a JVM, because the value of the property is cached by class loaders.
Java Web Start##