Java programs can be classified as either Java applications or Java applets,
based on the modules' execution content. While applets require the presence
of a Java-enabled browser (or an AppletViewer), applications are designed to
run on the client machine on the top of the Java interpreter, without the
need for special helper applications.
Separating applets and applications into two disjoined sets creates
inefficiency in software design, since programs designed to enrich browser
pages are usually not part of Java applications.
In this article, we propose a method to include applets as part of
applications. We discuss the similarities and differences between the
execution of applets and applications, and offer a brief outline on applet
design. And we propose a simple solution for adding applets with limited
functionality to Java applications. Next, we present a brie... (more)
Introduction
Large-scale distributed applications and shells often require the execution
of external modules. Because the modules are not known at compilation time,
this execution must be dynamic. For example, upon entering a command at the
UNIX prompt, the shell must find, load, and execute the requested program or
application. Although several methods have been found for loading (and
executing) dynamic Java classes, launching a Java Application from within
another Java program (applet or application) remains a difficult task.
This article presents a new method of loading and exe... (more)