-
Bug
-
Resolution: Fixed
-
P3
-
8, 9
-
b107
When launching an app without jnlp href directly from a command line:
javaws http://oklahoma.us.oracle.com/www/tests/1.9.0/hello/yescb.jnlp
(using full url to jnlp file) we have potential to cache the jnlp file both as the original url (yescb.jnlp) and as the canonical url (hello.jarjnlp).
We only want one entry, and since when launching the same app in other way (such as clicking on a link in a browser) we have no knowledge of the yescb.jnlp name and can only use the canonical name, we prefer to use the canonical name all the time.
In LaunchDownload.updateLaunchDescInCache() we take care of this the first time app is launched by calling ResourceProvider.get().markRetired on the cache entry for yescb.jnlp.
On subsequent invocations we do not do this, so if you run app from command line more than once, both entries will show in the cache viewer.
The fix is to make sure markRetired is called all of the time. (if all the conditions currently checked for the first time are met).
javaws http://oklahoma.us.oracle.com/www/tests/1.9.0/hello/yescb.jnlp
(using full url to jnlp file) we have potential to cache the jnlp file both as the original url (yescb.jnlp) and as the canonical url (hello.jarjnlp).
We only want one entry, and since when launching the same app in other way (such as clicking on a link in a browser) we have no knowledge of the yescb.jnlp name and can only use the canonical name, we prefer to use the canonical name all the time.
In LaunchDownload.updateLaunchDescInCache() we take care of this the first time app is launched by calling ResourceProvider.get().markRetired on the cache entry for yescb.jnlp.
On subsequent invocations we do not do this, so if you run app from command line more than once, both entries will show in the cache viewer.
The fix is to make sure markRetired is called all of the time. (if all the conditions currently checked for the first time are met).