Hi, Josh.
Is the 50 Mb you mentioned the size of your app alone or does that include the various GlassFish JARs as well?
If this size represents all the JARs, then if you revise your application Java Web Start would retrieve only the revised JAR. It would use the app server JARs cached on each individual system.
As for tweaking the generated JNLP - there's no supported way to do that. It's a frequently-requested enhancement and we very much want to do that in V3.
I'm afraid I do not have any suggestions for why the proxy solution would not be working. It sounds like the ideal approach.
One brute force approach would be to gain access to the training systems ahead of time and launch the app on each one to fill the local Java Web Start cache. But it sounds like that's not practical for you at this point.
Is the proxy software you are using able to display information about the requests it receives, whether it can resolve them against its own cache or whether it must fetch them from the actual source, and whether it actually caches a particular retrieved file? That might shed some light on what is or is not cached and/or resolved locally.
The ACC itself does not use any Java Web Start APIs that might fetch additional JARs, so whatever proxy usage (or lack thereof) occurs as Java Web Start itself fetches the required files.
Something else you might consider is looking into some of the javaws options. The -codebase one might help you. The developers guide
http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/contents.html
has a link on the bottom to the javaws command line description.
I'll keep thinking about this but those are some suggestions at the moment.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=215769