QZ Print issue

[Tres Finocchiaro]

Paris,

That is a good question.

It's all done within the jnlp now.  You can open it with a text editor to
see where the jar is referenced. You can't change it or rename it since
it's verified against a digitally signed version contained inside
qz-print.jar called JNLP-INF/APPLICATION.JNLP<http://i.imgur.com/IB3uWP2.png>
.

-Tres



*Tres Finocchiaro*
Owner, QZ Industries, LLC
support at qzindustries.com



On Thu, Oct 24, 2013 at 10:32 AM, Baughman, Paris <
Paris.Baughman at hydratight.com> wrote:

>  Hi Tres
>
> Thanks for your prompt reply, its very much appreciated
>
>
>
> A question :  If we remove the archive attribute, how does the application
> know where the qz print jar file is ?  Previously, using jzebra, we used
> the archive attribute to tell where the jar file is located ( or so I
> thought ?.. )
>
>
>
> thanks
>
>
>
> *Paris Baughman*
>
> Software Developer
>
>
>
> [image: Description: HT_logo (Small)] <http://www.hydratight.com/>
>
>
>
> *www.hydratight.com*
>
> * *
>
>
>
>
>
> *From:* tres.finocchiaro at gmail.com [mailto:tres.finocchiaro at gmail.com] *On
> Behalf Of *Tres Finocchiaro
> *Sent:* 24 October 2013 15:28
> *To:* Baughman, Paris; support at qzindustries.com
> *Subject:* Re: QZ Print issue
>
>
>
> Paris,
>
>
>
>    1. I would recommend removing the archive attribute as it is not
>    supported using the JNLP method.
>    2. Using the Java Control Panel, clear your cache as the old jnlp file
>    may be residual. *Delete it manually <http://i.imgur.com/Fa8F70g.png>* from
>    the Java Control Panel.
>    3. Also, this may be irrelevant, but I see you have nested double
>    quotes at @Url.Content.
>    4. Last, a trick for forcing the latest JNLP is to put some characters
>    after it (the JavaScirpt timestamp works well for this, but you can use
>    anything).
>    *<param name="jnlp_href" value="qz-print_jnlp.jnlp?test" />*
>
>
>
> -Tres
>
>
>
>
> *Tres Finocchiaro*
> Owner, QZ Industries, LLC
> support at qzindustries.com
>
>
>
> On Thu, Oct 24, 2013 at 8:59 AM, Baughman, Paris <
> Paris.Baughman at hydratight.com> wrote:
>
> Hi
>
> I need some help with regards to making the jar file work correctly
>
>
>
> I have added the jar and jnlp file to my project and also added the applet
> markup as follows :-
>
>
>
> <applet name="qz" archive="@Url.Content("~/Applet/qz-print.jar")" code
> ="qz.PrintApplet.class" width="55" height="55">
>
>     <param name="jnlp_href" value="qz-print_jnlp.jnlp" />
>
>     <param name="cache_option" value="plugin"/>
>
> </applet>
>
>
>
> And when I open my application I get the following message :
>
>
>
> CacheEntry[
> http://localhost:26070/DMS/en/WorkPackManager/Edit/qz-print_jnlp.jnlp]:
> updateAvailable=false,lastModified=Thu Jan 01 01:00:00 GMT 1970,length=11961
>
> JNLParseException[ Could not parse launch file. Error at line 61.]
>
>                 at com.sun.javaws.jnl.XMLFormat.throwNewException(Unknown
> Source)
>
>                 at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
>
>                 at
> com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
>
>                 at
> com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
>
>                 at
> com.sun.javaws.jnl.LaunchDescFactory._buildDescriptor(Unknown Source)
>
>                 at
> com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
>
>                 at
> com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
>
>                 at sun.plugin2.applet.JNLP2Manager.initialize(Unknown
> Source)
>
>                 at sun.plugin2.main.client.PluginMain.initManager(Unknown
> Source)
>
>                 at sun.plugin2.main.client.PluginMain.access$200(Unknown
> Source)
>
>                 at sun.plugin2.main.client.PluginMain$2.run(Unknown Source)
>
>                 at java.lang.Thread.run(Unknown Source)
>
> Error while initializing manager: JNLParseException[ Could not parse
> launch file. Error at line 61.], bail out
>
>
>
> Is something else I need to do in order to set it up correctly ?
>
>
>
> regards
>
>
>
> *Paris Baughman*
>
> Software Developer
>
>
>
> [image: Description: HT_logo (Small)] <http://www.hydratight.com/>
>
>
>
> *www.hydratight.com*
>
>
>
>
>
>
>
>
>  ------------------------------
>
>
> Actuant Corporation Email Notice
>
> This message is intended only for the use of the Addressee and may contain
> information that is PRIVILEGED and/or CONFIDENTIAL.
> This email is intended only for the personal and confidential use of the
> recipient(s) named above. If the reader of this email is not an intended
> recipient, you have received this email in error and any review,
> dissemination, distribution or copying is strictly prohibited.
> If you have received this email in error, please notify the sender
> immediately by return mail and permanently delete the copy you received.
>
> Thank you.
>
>
>
> ------------------------------
>
> Actuant Corporation Email Notice
>
> This message is intended only for the use of the Addressee and may contain
> information that is PRIVILEGED and/or CONFIDENTIAL.
> This email is intended only for the personal and confidential use of the
> recipient(s) named above. If the reader of this email is not an intended
> recipient, you have received this email in error and any review,
> dissemination, distribution or copying is strictly prohibited.
> If you have received this email in error, please notify the sender
> immediately by return mail and permanently delete the copy you received.
>
> Thank you.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/support/attachments/20131024/728a3a7f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 1475 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/support/attachments/20131024/728a3a7f/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1475 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/support/attachments/20131024/728a3a7f/attachment-0001.jpg>