JAR resources in JNLP file are not signed by same certificate

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load the sample page from the dist folder is latest update qz-print_1.6.8 - 
the first time will prompt to allow applet to run
2. If you close the sample.html page and open it again it will show the error: 
JAR resources in JNLP file are not signed by same certificate

What is the expected output? What do you see instead?
The applet will reload without error the second time the page is loaded

What version of the product are you using? On what operating system?
qz-print_1.6.8 on Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by jem.cast...@gmail.com on 22 Oct 2013 at 9:26

[GoogleCodeExporter]

Thanks for submitting this.  1.6.9 will have a signed jnlp file.  In the mean 
time, I've read that if you prefix "jnlp_" in front of all of your parameters, 
it correct this for unsigned jnlp files.  This success was reported by the 
Eclipse community here (your mileage may vary):
https://forums.oracle.com/thread/2593583

-Tres

Original comment by tres.fin...@gmail.com on 22 Oct 2013 at 11:53

• Changed state: Started

[GoogleCodeExporter]

Hi Tres

I downloaded the latest version 1.6.9 and the same issue occurs when I load the 
page twice. JAR resources in JNLP file are not signed by same certificate

How can I resolve this?

Jem

Original comment by jem.cast...@gmail.com on 23 Oct 2013 at 4:17

[GoogleCodeExporter]

Jem,

Thanks for the information.  Due to the new caching in Java 7 in conjunction 
with a bug in the way I was signing the code, I would recommend you:
1. Switch to 1.7.0 and 
2. Clear the QZ Plugin from the Java Control Panel Cache

I think then you should find you are fine.

Starting with qz-print-free_1.7.0, the applet will always check for a new JAR 
versions and it no longer requires the jssc and pdf-renderer libraries.

This should be much better moving forward.  Please post your progress.

-Tres

Original comment by tres.fin...@gmail.com on 24 Oct 2013 at 6:31

• Changed state: Fixed

[GoogleCodeExporter]

Tres,

This worked perfectly. Is there any issue with using this applet in a secured 
site: HTTS? Would the cert cause any issue?

Thanks for your assistance.

Jem

Original comment by jem.cast...@gmail.com on 24 Oct 2013 at 7:39

[GoogleCodeExporter]

Jem,

That is a fantastic question.  If you are just using a secure connection, it is 
actually recommended now from Oracle to use HTTP over HTTPS (you can hit "5" in 
the Java Console and read warning messages about NOT using HTTPS).

On the contrary, Java does have some cookie limitations which I'm not overly 
familiar with, so be mindful of that.

-Tres

Original comment by tres.fin...@gmail.com on 24 Oct 2013 at 8:29

[GoogleCodeExporter]

Tres,

It works now perfectly. Thanks.

Jem

Original comment by jem.cast...@gmail.com on 28 Oct 2013 at 2:11

[GoogleCodeExporter]

Is there any other way without installing the latest version to solve the above 
problem

Original comment by niteshpr...@gmail.com on 14 May 2014 at 9:46

[GoogleCodeExporter]

This issue is fixed.  If you have questions, please ask them here:
http://qzindustries.com/support

If you have a bug report to submit, please open a new one.

Original comment by tres.fin...@gmail.com on 14 May 2014 at 12:33