NonStop Server for Java 4.2 Programmer's Reference

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, 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.
Public Library Directory
Version 1 of the NonStop Server for Java 4 introduced a public library directory that has the default
name of /usr/tandem/java_public_lib.
For version 2 of the NonStop Server for Java 4, the default public library directory name changed to
/usr/tandem/java_public_lib_jdk142 because of the change to using version 3 of the C++
run-time library.
Note the following migration guidelines for using this directory:
You should not put any native libraries that use version 2 of the C++ run-time library in this
directory.
●
You can migrate version-neutral libraries, such as those written in C (for example, the JToolkit
library, libtdmext.lib) by copying them from /usr/tandem/java_public_lib to
/usr/tandem/java_public_lib_jdk142.
●
For more information about using the public-library directory, see Using the Makefile to Link in Native
Libraries. See, also, Binding Libraries into the JVM.
Floating-Point Support
By default, NonStop Server for Java 3.1.x and earlier versions converted any floating-point value that
crossed the Java Native Interface (JNI) boundary to a TNS float. This default could be overridden by
supplying a line in the file TandemVMClassFP.properties. If a particular class needed IEEE
floating-point values passed to its JNI code instead of TNS float values; users added a property (with the