Java Reference
In-Depth Information
files in detail in Chapter 9, “The Protocol.” For the rest, it is pretty similar to the
app.jnlp
main file.
L
ISTING
8.8
The splash.jnlp File
<?xml version=”1.0” encoding=”utf-8”?>
<jnlp spec=”1.0+”
codebase=”http://server/b2/c8/splash/”>
<information>
<title>A User-Friendly Splash Window</title>
<vendor>Mauro Inc.</vendor>
<homepage href=”home.html”/>
<description>Install Your programs via the Web, quickly and
effectively!</description>
<description kind=”short”>A simple Java-launched Installator</description>
<offline-allowed/>
</information>
<resources>
<j2se version=”1.3+”/>
<jar href=”splash.jar”/>
</resources>
<installer-desc main-class=”com.marinilli.b2.c8.splash.Splash”/>
</jnlp>
8
N
OTE
Different from the other examples, here the
jnlp
element does not have an
href
attribute. This is intentional. In this way, the JNLP Client doesn't put the application
in its list of available applications, and doesn't offer integration with the client OS.
However, it still continues to cache the application.
T
IP
The next time you launch the
app.jnlp,
you'll discover that the splash window does-
n't show up any more. Because it is an installer extension, the JNLP Client knows that
the application has been already installed, so it doesn't invoke the
splash.jnlp
file
any more. You need to manually locate the JNLP Client cache in the file system and
delete the cached files; then, the installation splash window will pop up again. Note
that this is the only way to go because the JNLP Client won't show the application in
the list of registered applications; thus, it is impossible to
selectively
clear the cache.
