Application Clients
Application Clients
client application written in the Java programming language that executes in the Java virtual
machine installed in the web browser. However, client systems will likely need the Java Plug-in
and possibly a security policy file for the applet to successfully execute in the web browser.
or security policy files are needed on the client systems. Also, web components enable cleaner
and more modular application design because they provide a way to separate applications
programming from web page design. Personnel involved in web page design thus do not need
to understand Java programming language syntax to do their jobs.
require a richer user interface than can be provided by a markup language. It typically has a
graphical user interface (GUI) created from the Swing or the Abstract Window Toolkit (AWT)
API, but a command-line interface is certainly possible.
application requirements warrant it, an application client can open an HTTP connection to
establish communication with a servlet running in the web tier. Application clients written in
languages other than Java can interact with Java EE 5 servers, enabling the Java EE 5 platform to
interoperate with legacy systems, clients, and non-Java languages.
architecture (JavaBeans components) to manage the data flow between an application client or
applet and components running on the Java EE server, or between server components and a
database. JavaBeans components are not considered Java EE components by the Java EE
specification.
properties. JavaBeans components used in this way are typically simple in design and
implementation but should conform to the naming and design conventions outlined in the
JavaBeans component architecture.
case of a client running in a browser, by going through JSP pages or servlets running in the web
tier.