Kbase 17708: Common causes of NoClassDefFoundError in Apptivity
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Common causes of NoClassDefFoundError in Apptivity
Common causes of the java.lang.NoClassDefFoundError:
You may get the NoClassDefFoundError message when deploying
an applet in Apptivity if there is a problem with aliases.
The following is a list of the aliases that need to be
set up in the web server to deploy an applet in Apptivity.
Please note that the aliases need to use forward slashes "/".
If "\" is used you may get the following message in the java
console -java.lang.NoClassDefFoundError
Directory Alias
c:\Apptivity20\jdbc /myapp/JDBC
c:\Apptivity20\netscape /myapp/Netscape
c:\Apptivity20\progress /myapp/Progress
c:\Apptivity20\com /myapp/Com
c:\InetPub\wwwroot\images /IMAGE_SOURCE
This is assuming you are using MicroSoft's IIS web server.
You may also get the NoClassDefFound error testing projects
in Apptivity Developer if the PATH or CLASSPATH settings are
not correct. Your environmental variables should include:
PATH=<INSTALLPATH>;<INSTALLPATH>\Java\bin;
CLASSPATH=.;<INSTALLPATH>;<INSTALLPATH>\Java\lib\classes.zip;
For more information about setting these variables please
refer to kbase 17622 Installing Apptivity: environment variables,
CLASSPATH, PATH
PES 02/26/98
Progress Software Technical Support Note # 17708