Java Reference
In-Depth Information
The value for each attribute is described in Chapter 10, “Defining the Client Environment.”
For example:
application__V1.2__Len_US__Len.jar
It instructs the JNLP server that the given resource is a named application, has a version “1.2”,
and supports two locales: American English and default English.
These files should be kept within the WAR file of the deployment servlet (see the Chapter 5
section on J2EE deployment for some detail on WAR files).
12
Another convention is to use an XML file in every directory we want to specify attribute val-
ues for the contained files. These files always have the standard name “v ersion.xml ”.
jnlp-versions within the root element can be only two possible elements: resource and
platform . The former is used for describing all the attribute values for a given physical
resource (that is, a file), whereas the latter is used to specify resources with a platform version
id. The elements pattern and file can be specified for any resource or platform giving
attribute values.
For example, Listing 12.1 shows a simple version.xml file that instructs the JNLP server that
file1.jar is the concrete file for the resource named resource1 ,supporting three different
languages, and with a current version “ 0.1.2 ”.
L ISTING 12.1
An Example of the version.xml File
<jnlp-versions>
<resource>
<pattern>
<name>resource1 </name>
<version-id>0.1.2</version-id>
<locale>en</locale>
<locale>it</locale>
<locale>es_ES</locale>
</pattern>
<file>file1.jar</file>
</resource>
</jnlp-versions>
Listing 12.2 proposes another example of version.xml file that shows the equivalence of the
two notations mechanism: that one based on the filename only, and this one based on XML
files.
Search WWH ::




Custom Search