Execution categories and executors


You can run typical Java applications using either internal or external execution, each of which have their advantages and disadvantages. Applets can be run using Applet Execution - see Applet viewer settings for more information. Java Server Pages can be run using JSP Execution - see Configuring JSP Execution Types. Other execution categories can be installed by extension modules.

External Execution

Most applications use external execution, and the templates that come with the IDE use it by default.

A new virtual machine (VM) is used for executing the application. This enables you to run applications that require a special VM or need to do operations that are not possible with internal execution (see below). You can specify the VM executable (such as java.exe) and complete command-line parameters together with class path settings for the application. External execution also protects the IDE from application crashes and delays.

Internal (Thread) Execution

An application run using internal execution runs inside the Forte for Java IDE. This brings the advantages that the application can modify the IDE itself and be loaded faster. But it imposes at least two restrictions on the executed application. The application cannot install its own URLStreamHandlerFactory or SecurityManager (so you cannot run RMI applications, for example). In addition, if the executed application crashes, the IDE crashes with it. Go to the Examples directory under the Filesystems tab in the Explorer to look at some samples of internal execution applications.

Note: Some applications, such as startup classes (in the Startup folder which can be accessed by choosing Tools | Global Options... from the main menu) require the use of internal execution because they are intended to modify the IDE itself.

Other execution categories

Other execution categories tailored for specific types of applications are installed by various modules, such as RMI and JSP.


Contents Prev Next Index