Kbase 18484: How the Apptivity IDE uses CLASSPATH To Run Java Application
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/11/1999 |
|
This document applies to: Apptivity Developer
Version and Release Number: 2.1 and 3.x
Summary:
When running a Java project, the Apptivity 2.1 IDE and 3.0 IDE use the
classpath set in the Project Properties and the system classpath
environment variable differently, depending on how you run the
project: in a browser, in the appletviewer, or in the JVM.
Details:
The project's classpath can be set by selecting Project->Properties
from the main menubar, and entering the desired value in the
Environment tab of the Apptivity Environment screen in the 2.1 IDE,
and in the Classpath tab of the Project Properties screen in the 3.0
IDE.
Both the 2.1 and 3.0 IDE execute a Java application with a
-classpath command line parameter which is used by the JVM in place
of the system classpath environment variable. This parameter uses the
value for classpath set in the project's properties.
For an applet run through the appletviewer, the 3.0 IDE will also
execute the appletviewer using a -J-classpath command line parameter,
which again uses the value for classpath set in the project's
properties.
The 2.1 IDE does not provide the classpath to the appletviewer as does
the 3.0 IDE, and so uses only the value of the system classpath
environment variable.
Browsers do not provide any way to pass classpath information
dynamically in the manner available to the appletviewer, so browsers
have to depend on the settings of the system classpath environment
variable.
References To Written Documentation or Other KnowledgeBase Documents: