Kbase 21333: Set and Change JAVA environment from Progress 9.1B (JDK 1.1.8) to Progress 9.1C ( (JDK 1.3)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
How to change and set JAVA environment variables in 9.1B and 9.1C?
GOAL:
What are the differences in JAVA environment variables between Progress 9.1B and Progress 9.1C?
FACT(s) (Environment):
Progress 9.1B
Progress 9.1C
FIX:
Since Progress supports 1.1.8 in V9.1B and 1.3 in V9.1C, some environmental changes related to CLASSPATH should be done accordingly if you are using your own script to set up Progres environment or use JDK/JRE provided by Progress on some platforms. If you use standard scripts (for example, proserve) from progress, no manual changes need to be done.
Following is extracted from JDK 1.3 documentation on how java and javac find the required classes. There are some significant changes between JDK 1.1.8 and JDK 1.3.
The Java launcher, java, initiates the Java virtual machine. The virtual machine searches for and loads classes in this order:
1. Bootstrap classes - Classes that comprise the Java platform, including the classes in rt.jar and i18n.jar.
2. Extension classes - Classes that use the Java Extension mechanism. These are bundled as .jar files located in the extensions directory.
3. User classes - Classes defined by developers and third parties that do not take advantage of the extension mechanism. You identify the location of these classes using the -classpath option on the command line the preferred method) or by using the CLASSPATH environment variable.
In effect, these three search paths are joined to form a simple class path. This is similar to the "flat" class path previously used in (JDK 1.1.8), but the current model has some important differences:
1. It is relatively difficult to accidentally "hide" or omit the bootstrap classes.
2. In general, you only have to specify the location of user classes. Bootstrap classes and extension classes are found "automatically".
3. The tools classes are now in a separate archive (tools.jar) and can only be used if included in the user class path. The jar file is only used when you use javac or javadoc.
Following is an example for windows,
For 9.1B,
JDKCP=%dlc%\jdk\lib\classes.zip
JRECP=%dlc%\jre\lib\rt.jar;%dlc%\jre\lib\i18n.jar
CLASSPATH needs to include JDKCP and JRECP and users classes such as progress. zip and jdbc.zip
For 9.1C, the above changed to:
JDKCP=%dlc%\jdk\lib\tools.jar
JRECP=%dlc%\jre\lib\rt.jar;%dlc%\jre\lib\i18n.jar
CLASSPATH only includes user classes