Issues with unsigned commons-httpclient.jar

[martinh]

I had the same problem. Marcel was informed about it 2 weeks ago.

I could solve this problem when updating java to 1.6 update 17.
For older versions of Java (for example 1.6 update 7 or even 1.5 the error occurs)
I upgraded all customers to 1.6 update 17 when it was possible.

[jcompagner]

yes older then u14 have a problem with double signing.

So i guess there are some jars now that have double signing and u13 can't handle this. It thinks that the jars are not signed with the same certificate (which i wrong because it is signed with the same but also with another)
it seem that u15 (and maybe u14) fixed this.

But if you find such a jar then i would say let the maker of that jar know that it is double signed, because then it can delete the other signing so it only has 1 signer so that it works in u13 and lower.

[ROCLASI]

I had the same issue with an 5.1.0 install with the latest it2be plugins.
The it2be-core has a jnlp that links to the Servoy /lib/log4j.jar. Since this is 5.1.0 it's not signed and it2be's stuff is so it barfs.
I had to hack out the log4j resource reference in the it2be jnlp to get it going again.
Not the best ways to fix things but it had to be done, it's a production server.

[IT2Be]

The problem that martin has is this:

we do replace %%serverURL%% in the jnlp files. You shouldnt really get that one
But it could be that marcel has an extension jnlp file that is targetted like: /plugins/somejardir/some3thpartyjnlp.jnlp

. I will solve that today or tomorrow.
The problem that robert described is something that I am evaluating right now.

[chico]

Awesome Marcel! It is appreciated.

[chico]

Hi Marcel! Any news on this?

Thanks so much.

Chico

[IT2Be]

Everybody that follows this thread, we released the following today:

1. Updated versions of our Components for Servoy 4/5 with updated JNLP files (see remarks Johan).

2. Updated versions of our Components for Servoy 3.5 with updated JNLP files (see remarks Johan).

3. Version 1.2 of our Components Manager (for Servoy 4/5).
When you use v1.2 of the Components Manager it will check for you if the version of Servoy is pre 4.1.6 or pre 5.1.2 and will, in that case, remove the security settings from the JNLP after downloading.
This should solve the issue the issue of mixing our signed Components with unsigned Servoy libraries.
You can download v1.2 of the Components Manager here: http://www.it2be.com/index.php/download ... oy-4-and-5.

[ROCLASI]

Very much appreciated Marcel.