--
You received this message because you are subscribed to the Google Groups "qz-print" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qz-print+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm wondering if the JAR is not seem from an executable point-of-view, either because of the JNLP file, or the MANIFEST file.
I tried several configurations for manifest attributes, such as "Trusted-Library: true", "Application-Library-Allowable-Codebase: *"...
Trusted-Library: true
Application-Library-Allowable-Codebase: *
Class-Path: lib/PDFRenderer-0.9.1.jar lib/jssc.jar
Application-Name: QZ Print Plugin
Permissions: all-permissions
Created-By: 1.7.0_76-b13 (Oracle Corporation)
Caller-Allowable-Codebase: *
Main-Class: qz.Main
Codebase: *
NB : Also, I always clear Java + browser caches between my tests.
I'll retry some JNLP/MANIFEST updates.
Cheers
Cheers
I'm going to proceed by step:
- Either I did too many copy/paste on the JAR file and he got corrupted: I'm gonna test the generated demo without signing the JARs.
- Either it's my JAR signing process or JNLP which is bad. Anyway I'll first try to fix it using the generated demo before embedding the JARs in my webapp.
I sign the 3 JARs (qz-print + PDFRenderer + jssc) with a valid certificate, using the following command:
%JAVA_HOME%\bin\jarsigner.exe -tsa http://timestamp.globalsign.com/scripts/timestamp.dll -storetype PKCS12 -keystore myCertificate.pfx -storepass myStorePwd qz-print.jar "1" -J-Dhttp.proxyHost=myProxyIP -J-Dhttp.proxyPort=8080
The JARs are successfully signed, and that was perfectly working 2 weeks ago. The things which have mainly changed during those 2 weeks are the switches between environments (some backups / re-integrations) and the JNLP/MANIFEST attributes.
Thanks again Tres.
#1.9 and higher
signing.tsaurl=http://fully.qualified.timestampauthority.url
signing.alias=my-java-signing-alias
signing.keystore=../path/to/keystore.ks
signing.keypass=S3CureP@SSW0RD
signing.storepass=S3CureP@SSW0RD
PS: the branch 2.0 you're talking about -> is this QZ Tray?
> PS: the branch 2.0 you're talking about -> is this QZ Tray?
Shortly, I'll probably have to study a replacement for QZ Print as Firefox will remove any support by the end of 2016. I didn't see any news for Internet Explorer, but it seems that Microsoft already broke the line with Edge not implementing NPAPI.
Thanks for your work!
Unfortunately the application users don't want to have any third party software installed on their PCs... for now :)
I'll probably have to study a replacement for QZ Print as Firefox will remove any support by the end of 2016. I didn't see any news for Internet Explorer, but it seems that Microsoft already broke the line with Edge not implementing NPAPI.