My application runs inside VisualAge, but not outside!

Scott Stanchfield

Some possibilities:

  • You Java Runtime Environment may not be properly installed.
  • Your external CLASSPATH isn't properly set. Make sure it includes the location of your application and anything the application references. Note that if your application resides in a jar file, the jar file must be on the CLASSPATH, not just the directory containing the jar file.
  • You don't have all the pieces you need to run the application. You may need to select additional classes to export as well. You can do this automatically by pressing the "Select referenced types" button in the export dialog. Note that this will not select dynamically-referenced types (types loaded via Class.forName()). This includes Swing's look and feel libraries. If running a swing application, it is best to get the Swing distribution from Sun (http://java.sun.com/products/jfc) and include its swingall.jar in your CLASSPATH
  • You may have exported only the source .java files. Make sure you selected .class. If you wanted source, make sure you compile the source outside VisualAge using your Java compiler.
  • Your Java Runtime Environment might not be a compatible version. For example, some browsers only support JDK 1.0.2, and VisualAge generates JDK 1.1+ compatible source. There are a few incompatabilities between JDK 1.1 and the Java 2 platform, particularly when compiling applications that use the List class and import java.awt and java.util. See http://java.sun.com/products/jdk/1.2/compatibility.html for compatability issues.

There are many other things that could be affecting your run. If you're still having trouble, we suggest you post the details on one of the VisualAge for Java newsgroups.


See also