Posted by qu0ll
on March 18, 2008 at 1:40 AM PDT
I am trying to use the new JVM parameters tag promised in Plugin2 for b13 by attempting to integrate with pack200 but no matter what I try I cannot get it to work.
Here's the APPLET tag:
and I have used pack200 to generate a file called myapplet.jar.pack.gz as per the documentation.
According to that documentation, by specifying the java arguments I am using then the class loader will first look for a file named myapplet.jar.pack.gz and, if it can't find that then look for myapplet.jar. This is not what is happening.
Using the applet tag as above and packaging just the compressed JAR in the WAR results in a ClassNotFoundException on the applet class. And then, even if I package the actual original JAR file in the WAR as well as the compressed version then it still can't find the applet class. However, if I remove the java arguments tag and include the original JAR it works properly.
So it seems that when specifying the -Djnlp.packEnabled=true JVM argument, the class loader doesn't work in any circumstances and can't even find the original uncompressed JAR.
Curiously, it is a little confusing as to what I should be naming the compressed JAR. In the documentation for Plugin2 it specifies that the file must be myapplet.jar.pack.gz but in the documentation for pack200, the example omits the ".jar" portion and thus the file name would be myapplet.pack.gz. It should be noted that I have tried both of these variations and neither work.
So does specifying the -Djnlp.packEnabled=true JVM argument actually work in b13 as promised? What do I need to do to get this to work?
And loving it,
(Replace the "SixFour" with numbers to email me)