no update-check on JNLP-file when start from other location than codebase
843802Jun 13 2006 — edited Jun 19 2006we are using JWS version 1.0 and 1.4.2.
Our clients have a common directory on the local disc which contains all the JNLP-files used in their organization. Some menu-links and some other applications are using this JNLP-files to launch and jump into the applications.
The JNLP-file repository is provided by an http-URL location. The JNLP-files in the local directory are directed by the codebase-attribute to this repository.
JWS processes the launch in following way:
1. read the codebase and href-attribute from the launched JNLP-file.
2. get timestamp from the original in the JNLP-repository
3. check if already cached and with latest timestamp.
4. download JNLP-file if not cached or not latest version.
5. check/download all other resources.
6. start the app.
With JWS shipped with JRE 1.5 (Beta was fine) this doesnt work in the same procedure:
1. copy the launched JNLP-file in the empty JWS-cache.
2. set a new timestamp on the cached JNLP-file (it does not let the old timestamp).
3. get timestamp from the original in the JNLP-repository (given with the codebase & href attribute)
4. check if already cached and with the latest timestamp.
5. download JNLP-file if not cached or not latest version. (will never appear because timestamp in cached version is newer)
6. check/download all other resources.
7. start the app. (with probably not latest resources)
Is this behaviour ok or is this a Bug?