Configuring the Executors That Run Your Programs

The IDE runs a program using an executor. An executor specifies the java launcher (or appletviewer) to use, its arguments, and other information, such as the path that the IDE uses to look up classes and the working directory.

The IDE provides a set of default executors that suit most development tasks. This set includes the external and internal executors for running applications and the applet executor for launching applets. (The IDE might also include an executor for a specific type of application, such as RMI and JSPTM, if you installed those modules.)

External Executor

The external executor is the default executor provided with most templates in the IDE. When you use an external executor, the IDE calls a new virtual machine (VM) when it executes the application. This enables you to run applications that require a special VM and to perform operations that are not possible with internal executors. For example, you can specify the VM executable (such as java.exe) and complete command-line parameters together with class path settings for the application. Using an external executor also protects the IDE from application crashes and delays.

By default, the external executor calls the java command associated with your JDK. For more information on the java command, see http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/java.html

Internal Executor

An application that is run using the internal executor runs inside the IDE. Although running the executor within the same virtual machine as the IDE is faster, it imposes two restrictions on the executed application:

Some applications, such as startup routines, require an internal executor because they modify the IDE. The Examples directory provided with the IDE provides sample applications that are executed internally.

Applet Executor

By default, the IDE launches an applet in the applet viewer (using the appletviewer command provided with your JDK). You can change the applet executor so that an applet runs in the web browser of your choice. Running an applet in a web browser can be slower than using the applet viewer because the web browser has to startup. However, before deploying your applet, you should verify that it displays in external browsers.

For more information on the appletviewer command, see http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/appletviewer.html

For information on configuring the executors in the IDE, see:

Specifying the Default Executor for a Class

Specifying the Default Executor for a Project

Configuring the External Executor

Configuring the Applet Executor

Configuring the JSP Executor

Defining a New Executor Type

Removing an Executor Type

Legal Notices