Java Reference
In-Depth Information
F
Avoid excessive JAR update checks
—JavaFX applets and Web Start applications will
automatically check for updates for the JAR files included in your application upon
startup. You can either turn that off (if you don't plan on having updates), or do the
update in the background by specifying it in your JNLP file as follows:
<jnlp>
...
<update
check="background"/
>
</jnlp>
F
JAR versioning—if
—if you decide to have your JARs be updated automatically
(see previous bullet point) you can use JNLP's JAR-versioning mechanism.
It uses this mechanism to update JAR files when version number changes,
instead of checking for updates for all JARs. To take advantage of this, name
your JARs using this format
{jar-name}_V{version-number}.jar
, for example
demo-util_V1.0.jar
. Then, set the
jnlp.versionEnabled
attribute
in the JNLP file as shown:
<jnlp>
...
<resources>
<jar href="demo-app.jar" main="true"/>
<jar href="demo-util.jar"
version="1.0"/>
<property name="
jnlp.versionEnabled
" value="true"/>
<resources>
</jnlp>
F
Avoid signing your application
—while a properly signed application can establish a
certain level of trust, signing, however, can introduce new dialogue boxes that force
users to confirm their trust in the application issuer. So, unless you absolutely need
signing, avoid it. An unsigned application causes a security dialogue to appear only
when the application attempts to execute privileged code. Furthermore, users can
opt to trust the the unsigned application and no longer be presented with future
security warnings.
