After a quick market search, we discover that the available third-party tools are too expensive
for our budget. Hence, the most obvious choice is to implement in-house the wanted service,
without changing the Java edition and saving all other costs but development. This option is
represented by point B in Figure 4.5.
Other choices are possible, though. Point C corresponds to using a standard J2SE JRE, imple-
menting our old application as an applet and using the Plug-In facility included into the JRE
distribution. This has a cost in porting the existing software to the Java 2 platform and trans-
forming it in an applet, but then there are no other costs for the developers.
The other possible option is to employ the JNLP technology (point D). This way, automatic
updates are achieved by the locally installed JNLP client, and only the porting from JDK 1.1.x
to J2SE is needed.
……Ad-Hoc Deployment Services
………Advanced Deployment Services
……………JNLP 1.0 Deployment Services
……“One shot” Deployment
F IGURE 4.5
The Deployment Design Box used for studying alternative deployment solutions.
Each arrival point (that implies a different deployment circuit enhancement strategy) has its
own characteristics. Point B implies some coding effort that is absent in the other choices. On
the other hand, Points C and D need a code upgrade to J2SE; this could be a problem in some
Concrete examples of adding deployment services to old Java code are discussed in Chapter 6.