Skip to main content

Version download and Pack200 support

2 replies [Last post]
pgokhale
Offline
Joined: 2006-02-07

Hello,

Have couple of questions about the new plugin's versioning and pack200 support:
1. Testing Guidelines documentation (https://jdk6.dev.java.net/testProperty.html) mention that "jardiff is not supported in version download". Does this mean that the version string specified in jnlp is alone compared with the jar name on the server and even if I 'managed' to put a different version of this jar with same name, the plugin won't download it since it didn't compare it with what was cached on the client?

2. If I have both, packEnabled and versionEnabled, properties set to true and mention a jar name in jnlp file and also put this name under classpath in some other jar's manifest file (as a required dependency), I see the applet makes three server requests (in tomcat's access logs):

jnlp

..

..

tomcat access logs:
"GET /app/jcommon__V1.0.9.jar.pack.gz HTTP/1.1" 200 89838
..
"GET /app/jcommon.jar.pack.gz?version-id=1.0.9 HTTP/1.1" 404 1039
"GET /app/jcommon.jar?version-id=1.0.9 HTTP/1.1" 200 89838
--

Any ideas how to avoid this additional overhead of plugin making two requests for the same jar (that too when the first request was successful).

appreciate your help.

Parag

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kbr
Offline
Joined: 2003-06-16

Please file a bug and provide a test case. I don't know whether there is a workaround possible aside from enabling Pack200 support on your server.

pgokhale
Offline
Joined: 2006-02-07

I should add that the war contains both
jcommon__V1.0.9.jar and jcommon__V1.0.9.jar.pack.gz