Name: dfR10049 Date: 02/16/2004



JNLP 1.5 spec states:
     The version attribute can not only specify an exact version, as shown
     above, but can also specify a list of versions, called a version string.
     A version string is an ordered list of version-ranges separated by spaces.
     A version range is either a version-id, a version-id followed by a star
     (*), a version-id followed by a plus sign (+) , or two version-ranges
     combined using an ampersand (&). The star means prefix match, the plus
     sign means this version or greater, and the ampersand means the logical
     anding of the two version-ranges. For example:

     <jar href="classes/MyApp.jar" version = "1.4.0_04 1.4*&1.4.1_02+" />

     The meaning of the above is: the JAR file at the given URL that either has
     the version-id 1.4.0_04, or has a version-id with 1.4 as a prefix, and not
     less than 1.4.1_02. The exact syntax and definition of version-ids and
     version strings is given in appendix A.

So resource version "1.4.1_05" satisfies pattern from example should be
accepted by JNLP client, but it is not accepted. I got the following
error message:

#### Java Web Start Error:#### Bad version in response from server when
accessing resource:
(http://volvo:34536/http_requests/VersionBasedProtocol/version_and.jar,
1.4.0_04 1.4*&1.4.1_02+) - 1.4.1_05

(I use JDK build 1.5.0-beta2-b37)

======================================================================