NonStop Server for Java 5.0 Programmer's Reference

For Java Based Products
Before version 1 of the NonStop Server for Java 4 (based on J2SE SDK 1.4.0), no guidelines
were provided for where Java based products should install their JAR files. Many of these
products installed their JAR files in the /usr/tandem/java/jre/lib/ext directory.
Occasionally, the installation of a Java based product would overwrite a JAR file required by
another Java based product, possibly causing a version mismatch.
In addition, Java based products had to be reinstalled whenever NonStop Server for Java issued
a new product version.
For these reasons, beginning with version 1 of the NonStop Server for Java 4, HP recommends
that the JAR files associated with Java based products remain in a product-specific directory.
When you follow this recommendation, you must include the JAR files of the Java based
product in either your CLASSPATH environment variable setting or the -classpath (-cp)
command-line argument.
User-Provided JAR Files
Previously, many users also installed JAR files in /usr/tandem/java/jre/lib/ext
because they did not have to include such JAR files in their CLASSPATH. Beginning with
version 1 of the NonStop Server for Java 4 (based on J2SE SDK 1.4.0), HP recommends you do
not install user-provided JAR files in any directory of versions 1 and 2 of the NonStop Server
for Java 4 tree. You should leave the JAR files in user-specific directories. If you follow this
recommendation, you will not have to reinstall user-provided JAR files for new product releases
of NonStop Server for Java 4. You, however, have to place the JAR files in your CLASSPATH.
Dynamic Link Libraries (DLLs)
On the TNS/E platform, NonStop Server for Java 4 and 5 support Dynamic-Link Libraries
(DLLs). All NonStop Server for Java applications migrating from TNS/R to TNS/E must
convert native libraries to DLLs.
Consider these issues when migrating applications to use DLLs with the NonStop Server for
Java 5:
All the Java libraries are built as DLLs.●
When using the JNI code, use DLLs instead of static libraries. For further information,
see Java Native Interface (JNI). A public library directory does not apply for Java
applications on the TNS/E platform.
●
All DLLs must be in files that have specific naming requirements. For further
information see DLL names.
●