General JNLP examples:
• Test application (Listings 8.1-3) shows how to use local file system resources with
•A simple example of a basic yet complete JNLP deployment is provided in the editor1
application (Listings 8.4-6).
• An example of lazy resource usage is the LazyEditor application (Listings 10.3-5).
• The security demo shown in Listings 10.7-8 provides an example of the security model
of JNLP 1.0. It uses JNLP runtime services as well.
• The Tex t uale application (see Chapter 13) provides a complete JNLP application deploy-
ment example, featuring among the others: ad-hoc installer support, lazy resources.
•Version management classes (see Chapter 12, “Server-side Deployment Support”) pro-
vide a package for implementing version-based management. They could be used within
a servlet environment for providing JNLP versioned download. A front-end test GUI
class is supplied for direct testing.
Examples of the use of JNLP runtime services are the following:
• Splash window (Listings 8.7-11).
• Native code installer (Listings 9.3-7).
• Customize the JNLP Client's download window (Listings 9.14-15).
• FileContents manipulation (Listing 11.3).
• DownloadService example (Listing 11.4).
•Printing example via JNLP (Listing 11.9).
• The Tex t uale application (see Chapter 13) provides another installer example, similar to
the download window customization example of Chapter 9, “The JNLP Protocol.”
• Optional packages installation example (Listings 11.6-8).
JNLP general utility, reusable code:
• The Utilities class (Listing 11.1). A “lightweight” utility class that provides simpler
JNLP runtime services access, internationalization support, and robust icon and resource
acquisition services. It doesn't automatically handle standalone application execution (it
doesn't require the utility package in Appendix D).
•A JNLP label (Listing 11.2). A Swing component that shows a clickable URL-like label
that brings up a Web browser window. The label text and URL address are separated.
•A persistence wrapper class (Listing 11.5). It wraps JNLP persistence services, provid-
ing—among other services—a serialization-like interface for reading and writing objects
identified with simple strings or complete URLs.