[Bug 3583] When creating Desktop Short Cuts for JNLP files, javaws links to path specified by Firefox (temporary)

[bugzilla-daemon at icedtea.classpath.org]

https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3583

--- Comment #5 from JiriVanek <jvanek at redhat.com> ---
(In reply to Robert Marcano from comment #4)
> I think probably a good behaviour for javaws is to not offer to create
> desktop launchers for JNLP files that don't include a way to get the source
> path, or copy it a .local/.cache directory.

How to determine this? You may have local installation of some JNLP
application, so you can run  javaws /some/path/to/file.jnlp or  javaws
file:///some//path/to/file.jnlp 

We can catch vartious /tmp or $TEMP but more hardly firefox special  cache.
also I have no idea how to make it windows portable...

> 
> The problem with caching it is that every time the user uses the web link to
> start the application it will think it is a new one. Unless the files cached
> are hashed and tested if there is already one downloaded, but a single
> change on the source JNLP will make javaws think it is a new one.

This is actually done.  ITW checks timestamps of files. If the files were not
updated on server, and jnlp application is correct, then ITW will nto download
it again.

Also there is --Xoffline switch which enforce ITW to not even try remote
locations and simply goes from what is cached.   The Xoffline switch is holly
grail  for all jnlp offline usages.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20180514/94526972/attachment.html>