Inter-JVM (External) Validation
In order to validate a Java GUI that either does not meet the criteria for an
Internal validation or one for which you do not have the source code,
use the Java
Application with ACTF launch configuration. Note: The Java
Application with ACTF launch configuration is available only in run
mode and not in debug mode.
To launch a Java Application with ACTF:
- In the Plug-in Development Perspective or Java
Perspective choose Run->Run... from the main Eclipse
menu-bar.

- If you already have an ACTF Java Launch configuration, skip
this step. If this is the first configuration of this type you have
attempted to launch, the dialog will look something like this:
- Select Java Application with ACTF from the list. In
Eclipse 3.2, right-click on this item and select New or click on
the New button
.
In earlier versions of Eclipse, simply press the New button once
the type is selected. Give your configuration a name and for the Main
class, enter name of the class you wish to validate. We're going to use
SwingSet2.
- Click the Classpath Tab and select "User Entries" and click
the "Add External JARs" button. Use the dialog to navigate to the
necessary jar archive (eg: SwingSet2.jar). Save the configuration
changes by selecting Apply.
- Press the Run button to launch the desired Java
application.
- As you work in the newly launched Java application, validation
violations will be generated and put into the Validation Report
View.

Important: Be sure that the appropriate system properties
are present for your JVM version on the AOP Properties
Preferences Page. These include:
- osgi.parentClassloader = app (all JVM versions)
- osgi.install.area = <eclipse installation location>
(JVM1.4.2)
- osgi.logfile = <any log file, preferably in eclipse
installation directory> (JVM1.4.2)