Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Webstart RCP (based on eclipse 3.6.2)
Webstart RCP (based on eclipse 3.6.2) [message #660198] Thu, 17 March 2011 10:05 Go to next message
Elvis Dominguez is currently offline Elvis Dominguez
Messages: 52
Registered: July 2009
Location: Switzerland
Member
Hi all,

i'm releasing our RCP solution via webstart.
everything ran smoothly until yesterday when I updated eclipse to 3.6.2
(delta pack too).

Now the client can't start, raising an error like:
com.sun.deploy.net.FailedDownloadException: Impossibile caricare la
risorsa: http://myserver/app/plugins/
org.eclipse.core.runtime.compatibility.registry_3.3.0.v20100 520.jar


wrapped exception says

java.io.IOException: invalid SHA1 signature file digest for
runtime_registry_compatibility.jar

runtime_registry_compatibility.jar is an archive packed in the root of
the plugin o.e.c.r.compatibility.registry_3.3.0.v20100520.jar

I sign my jars with our certificate, and if i look inside the internal
jar i see, in the META-INF, our signature files.

Some idea?

--
kindly Elvis Dominguez
Re: Webstart RCP (based on eclipse 3.6.2) [message #660386 is a reply to message #660198] Fri, 18 March 2011 08:54 Go to previous messageGo to next message
Elvis Dominguez is currently offline Elvis Dominguez
Messages: 52
Registered: July 2009
Location: Switzerland
Member
On Thu, 17 Mar 2011 10:05:15 +0000, Elvis Dominguez wrote:

> Hi all,
>
> i'm releasing our RCP solution via webstart. everything ran smoothly
> until yesterday when I updated eclipse to 3.6.2 (delta pack too).
>
> Now the client can't start, raising an error like:
> com.sun.deploy.net.FailedDownloadException: Impossibile caricare la
> risorsa: http://myserver/app/plugins/
> org.eclipse.core.runtime.compatibility.registry_3.3.0.v20100 520.jar
>
> wrapped exception says
>
> java.io.IOException: invalid SHA1 signature file digest for
> runtime_registry_compatibility.jar
>
> runtime_registry_compatibility.jar is an archive packed in the root of
> the plugin o.e.c.r.compatibility.registry_3.3.0.v20100520.jar
>
> I sign my jars with our certificate, and if i look inside the internal
> jar i see, in the META-INF, our signature files.
>
> Some idea?

Just as info: if I export the app using the File > Export than the jar in
signed correctly...



--
kindly Elvis Dominguez
Re: Webstart RCP (based on eclipse 3.6.2) [message #673604 is a reply to message #660198] Tue, 24 May 2011 08:40 Go to previous messageGo to next message
Christian Minke is currently offline Christian Minke
Messages: 1
Registered: May 2011
Junior Member
Hi,

had the same problem. Seams that jarsigner doesn't like to sign signed packages.

Just remove:
- META-INF/eclipse.inf
- META-INF/ECLIPSE.RSA
- META-INF/ECLIPSE.SF

If you only work with the jar, you'll somewhere find an howto to unpack, remove and pack it.
e.g.:
jar -xvf ../plugin.jar
rm META-INF/eclipse.inf
rm META-INF/ECLIPSE.RSA
rm META-INF/ECLIPSE.SF
edit META-INF/MANIFEST.MF
jar cvf ../plugin.jar META-INF/MANIFEST.MF *


Good luck!
Re: Webstart RCP (based on eclipse 3.6.2) [message #673720 is a reply to message #673604] Tue, 24 May 2011 14:37 Go to previous messageGo to next message
Elvis Dominguez is currently offline Elvis Dominguez
Messages: 52
Registered: July 2009
Location: Switzerland
Member
Hi

What I have additionally found is, as said, that exporting manually from eclipse the applications runs ok.
I have checked generated jars and they are signed only with my own certificate (but only if I tick the 'generate jnlp...' in export dialog!).
When I build my plugins with the ant task then eclipse jars (swt, osgi, ...) are signed with eclipse certificate.
This results in jars with double signing.

Is there a way to tell the eclipse build plugins ant task to not sign exported plugins?

Sorry for bad english
Kindly

Elvis D.
Re: Webstart RCP (based on eclipse 3.6.2) [message #673723 is a reply to message #673604] Tue, 24 May 2011 14:42 Go to previous message
Elvis Dominguez is currently offline Elvis Dominguez
Messages: 52
Registered: July 2009
Location: Switzerland
Member
Christian Minke wrote on Tue, 24 May 2011 10:40
Hi,

had the same problem. Seams that jarsigner doesn't like to sign signed packages.

Just remove:
- META-INF/eclipse.inf
- META-INF/ECLIPSE.RSA
- META-INF/ECLIPSE.SF

If you only work with the jar, you'll somewhere find an howto to unpack, remove and pack it.
e.g.:
jar -xvf ../plugin.jar
rm META-INF/eclipse.inf
rm META-INF/ECLIPSE.RSA
rm META-INF/ECLIPSE.SF
edit META-INF/MANIFEST.MF
jar cvf ../plugin.jar META-INF/MANIFEST.MF *


Good luck!


Thank you for your tip. That was the problem.
Previous Topic:Drop down menu below main menu programmatically
Next Topic:(no subject)
Goto Forum:
  


Current Time: Tue Sep 02 23:59:32 GMT 2014

Powered by FUDForum. Page generated in 0.01989 seconds