Plugin and Beans with Java 6 update 19

Classic Servoy
61

Thomas Parry:
I also had same message for the Spellcheck pro plugin. Then I went into the jnlp file for it and noticed that the version= part was not the recommended version=“%%version%%” so I manually changed them and then that exception seemed to go away. I checked the jnlp for the it2be-tools and it is fine. So it is one or more jar files in the plugin sub-folder that it does not like.

What happens when you clear your cache first on the client machine? I know Johan fixed an issue the jnlp version strings in 5.1.3 but I am not sure if this ever got into 3.5.12.

62

Patrick,
the signtester now does not crash.

It still shows lots of not verified jar files.

No change in the exception when attempting to download the smart client.

63

I am clearing the cache before every restart of the server.
No changes - still stops on the first “not verified” jar file.

As an experiment I could omit the it2be-tools and try again - I suspect that it will fail on the next not verified jar file.

(My client is not exactly happy to be down at this moment!) :oops:

64

Thomas Parry:
Patrick,
the signtester now does not crash.

It still shows lots of not verified jar files.

No change in the exception when attempting to download the smart client.

You can’t use it on if server or developer is running!!!

The jars are locked so they can’t be modified/signed, I guess that’s what is happening to you.

65

Thomas Parry:
I am clearing the cache before every restart of the server.
No changes - still stops on the first “not verified” jar file.

As an experiment I could omit the it2be-tools and try again - I suspect that it will fail on the next not verified jar file.

(My client is not exactly happy to be down at this moment!) :oops:

You could also clear the server cache (/application_server/server/work/catalina/yourhost/)…

66

I always run the signtester with the server shutdown.

As a last resort I wacked the offending it2be-tools suite of files and folders then downloaded the complete latest set and re-installed it.
Interestingly now these files are verified with the signtester tool. So my method of updating the plugins appears to be flawed to say the least!

Now downloading the smart client completes properly.

So I will assume this was the correct remedial action.

Thanks for the advice from all.

67

I have replaced the jasperreports-3.7.1.jar by the version 3.7.3 file on my Servoy 5.1.4 application server.
Launching the Smart Client from Developer I get no error messages, but when launching the Smart Client from the application_server, I get the error:

<>
<<Error: Found unsigned entry in resource: (http://xxx.xxx.xxx.xxx:8080/plugins/ser … -3.7.3.jar, 1275474554000)>>

Of course, I have changed the setting in the jnlp file.

If I run now the signtester.jar the unsigned jasperreports-3.7.3.jar will be dedected. I have signed it like Johan has discribed it in a previous post on this topic and the tool returns all files are signed. But while launching the Smart Client again, I get the error message:

<<Error: JAR resources in JNLP file are not signed by same certificate>>

What can I do to get it work?

68

are you sure, you use the latest signtester.jar from Servoy-stuff site??

clear your cache, (and what I mostly do, is clear the catalina cache folder also on the servert)

69

where do you get jasperreports-3.7.3.jar from?

If you just download them from somewhere and dump it into the plugin. Then yes it has to be signed
But you cant sign that jar file with the same certificate as the original plugin is signed (thats servoy certificate)
So if you just update jars inside a plugin that is already signed by somebody else then you need to resign the whole plugin (so all the jars that the jnlp file of that plugin points to)

70

Harjo:
are you sure, you use the latest signtester.jar from Servoy-stuff site??

clear your cache, (and what I mostly do, is clear the catalina cache folder also on the servert)

Thanks Harjo!

I used the latest signtester.jar and cleared also the catalina cache, but Johan got it.

71

jcompagner:
where do you get jasperreports-3.7.3.jar from?

If you just download them from somewhere and dump it into the plugin. Then yes it has to be signed
But you cant sign that jar file with the same certificate as the original plugin is signed (thats servoy certificate)
So if you just update jars inside a plugin that is already signed by somebody else then you need to resign the whole plugin (so all the jars that the jnlp file of that plugin points to)

Hi Johan,

I got the jasperreports-3.7.3.jar file from my iReport 3.7.3 installation. How do I resign the whole plugin?

72

that you can also do with the latest signtester.jar from Mr Patrick…

http://forum.servoy.com/viewtopic.php?f … 188#p74828

73

tgs:

Harjo:
are you sure, you use the latest signtester.jar from Servoy-stuff site??

clear your cache, (and what I mostly do, is clear the catalina cache folder also on the servert)

Thanks Harjo!

I used the latest signtester.jar and cleared also the catalina cache, but Johan got it.

Hi Harjo,

actually I don’t used the latest signtester.jar (I had Johan’s vers.) :cry: . But now I have the right one from the Servoy-Stuff site!
Could you please post the correct command line incl. the ‘overwrite’ parameter? This would be very glad.

74

try

java -jar signtester.jar

first
that will give you the options

75

Ok, the output now in the termial is:

Verifiying dir: ./plugins/servoy_jasperreports/Applications/Servoy5/application_server/./plugins/servoy_jasperreports/jasperreports-3.7.3.jar didnt verify

All others are verified.

Do I run now the unsigner.jar and than sign again with the signtester.jar?

76

jcompagner:
try

java -jar signtester.jar

first
that will give you the options

oeps thats true, default it just verifies
just give a argument with it:

java -jar signtester.jar x

and then it will explain what you can call

77

Johan,

I have now signed the jar files by my own generated kestore how you explained.
When I run the signtester.jar again, all the Verifying dirs are signed.
Than I have deleted the server cache and also the .servoy folder and Java cache files on the client side. Made a restart of the server, but still the same error while launching the smart client:

Error: JAR resources in JNLP file are not signed by the same certificate

What is wrong?

78

Hi Thomas,

can you please post the details of the ‘JAR resources in JNLP file are not signed by the same certificate’ error here?
This gives good information which jars are involved here.

79

This are the resources of the jnlp file:

<?xml version="1.0" encoding="UTF-8" standalone="no"?><jnlp codebase="http://192.168.1.11:8080" href="/servoy-client/plugins/servoy_jasperreports.jar.jnlp" spec="1.0+">
	<information>
		<title>Servoy Client Plugins</title>
		<vendor>Servoy and Others</vendor>
	</information>
	<resources> 
		<jar download="eager" href="/plugins/servoy_jasperreports.jar" version="1274455126000"/>
		<jar download="eager" href="/lib/commons-collections.jar" part="commons-collections" version="1270212958000"/>
			<package name="org.apache.commons.collections.*" part="commons-collections" recursive="true"/>
		<jar download="eager" href="/lib/commons-logging.jar" part="commons-logging" version="1270212963000"/>
			<package name="org.apache.commons.logging.*" part="commons-logging" recursive="true"/>
		<jar download="eager" href="/lib/commons-dbcp.jar" part="commons-dbcp" version="1270212959000"/>
			<package name="org.apache.commons.dbcp.*" part="commons-dbcp" recursive="true"/>
			<package name="org.apache.commons.jocl.*" part="commons-dbcp" recursive="true"/>
		<jar download="eager" href="/plugins/servoy_jasperreports/jasperreports-3.7.3.jar" version="1276082068000"/>
		<jar download="eager" href="/plugins/servoy_jasperreports/commons-beanutils-1.8.0.jar" part="commons-beanutils" version="1274454356000"/> 
			<package name="org.apache.commons.beanutils.*" part="commons-beanutils" recursive="true"/> 
		<jar download="eager" href="/plugins/servoy_jasperreports/commons-digester-1.7.jar" part="commons-digester" version="1274454356000"/> 
			<package name="org.apache.commons.digester.*" part="commons-digester" recursive="true"/> 
		<jar download="eager" href="/plugins/servoy_jasperreports/iText-2.1.7.jar" part="itext" version="1274454358000"/> 
			<package name="com.lowagie.*" part="itext" recursive="true"/> 
		<jar download="eager" href="/plugins/servoy_jasperreports/jdt-compiler-3.1.1.jar" part="jdt-compiler" version="1274454362000"/> 
			<package name="org.eclipse.jdt.*" part="jdt-compiler" recursive="true"/> 
		<jar download="eager" href="/plugins/servoy_jasperreports/poi-3.5-FINAL-20090928.jar" part="poi" version="1274454364000"/> 
			<package name="org.apache.poi.*" part="poi" recursive="true"/> 
	</resources> 
	<component-desc/> 
	<security>
		<all-permissions/>
	</security>
</jnlp>
80

did you use the overwrite parameter of the signtester?

You really have to resign everything, you still seem to have mixed signing in jnlps