Servoy plugins not signed problem

Classic Servoy
1

Hi,

I have done a new installation of servoy 5.1 and I have update it to 5.1.2 version.
I’m using java 1.6 update 20.

I don’t use third part plugins but an error occur when I try to launch the smart client from my application server.
This error tell me that there is a plugins that haven’t the signature:
[attachment=0]servoy_client_problem.JPG[/attachment]

servoy_client_problem.JPG
servoy_client_problem.JPG1043×705 106 KB

2

Hi Marco,

this is exactly the same problem as the one in this thread http://forum.servoy.com/viewtopic.php?f=6&t=14035#p73733
And the resolution is also to set the version of the excelxport.jar.jnlp jar nodes to %%version%%

Optionally you can clear your client’s cache.

3

Ok!

Deleting both cache and temporary file all work fine! with deleting only the cache it doesn’t work!I haven’t done any else.

Thanks for the suggestion Patrick!

Marco

4

Version: 5.1.2 - build 959
Java 6 U18 (1.6.0_18)

I performed a new install of Servoy 5.1.2 on our server, then ran the signtester.jar program which ran through all the plug-in .jnlp files successfully (no reported problems).

From one computer in our office, I can successfully launch a Servoy solution, but from another computer I get a client-generated exception for the same solution:

com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: (http://192.168.1.90:8080/plugins/pdf_output/itext.jar, 2.0.3)
at com.sun.javaws.security.SigningInfo.getCommonCodeSignersForJar(Unknown Source)
at com.sun.javaws.security.SigningInfo.check(Unknown Source)
at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
at com.sun.javaws.Launcher.prepareResources(Unknown Source)
at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

I read elsewhere on the forum that the client cache needs to be cleared, so I suspect this may be the problem. How do you clear the client cache? Also, do I need to modify the pdf_output .jnlp file?

Thanks!

5

If you modify all the jnlp and make sure you use version=“%%version%%”, then your clients should see that there is a new version of the jars and download them.