Every time I click on the .jnlp to launch my WebStart JOGL app, it downloads the JOGL jar and natives. Is there any way to tell it to cache JOGL, so that it isn’t an extra 1.1MB download every time someone launches the app?
Thanks
Every time I click on the .jnlp to launch my WebStart JOGL app, it downloads the JOGL jar and natives. Is there any way to tell it to cache JOGL, so that it isn’t an extra 1.1MB download every time someone launches the app?
Thanks
Are you referring to the jogl.jnlp file hosted on java.net in your application’s JNLP file? If so, I think the JOGL jars shouldn’t be being re-downloaded each time. There was a problem on the java.net web servers where they were sending the current timestamp as the files’ modification time, confusing JWS, but I thought that problem had been fixed.
Yes, that’s exactly the problem - I’m referencing https://jogl.dev.java.net/webstart/jogl.jnlp from within my own JNLP.
If this is a bug which has cropped up before, can you tell me who I should contact about it? (Someone at Sun I presume.)
Thanks.
If the bug is still there (or has reappeared), it’s a bug in the java.net web servers where they are serving up incorrect timestamps in HTTP HEAD requests which are used by Java Web Start to determine whether the cached copy of a part of an application has to be invalidated and re-downloaded. I emailed some people about this a while back and it seemed at one point to have been fixed but I can’t test right now because the web start binaries are actually broken and I’m planning to do a rebuild and redeployment. Probably the best way for you to get action on the issue is to file a bug with the java.net Issue Tracker at https://java-net.dev.java.net/servlets/ProjectIssues .