Does client.second have a dependency on the compute.jar? And if so, is that jar signed? My primary experience with signed JARs is with Java Web Start and Applets. And for those, all the secondary jars also need to be signed. I can't remember what error you get if they are not. I'm not sure if the same requirement holds for running signed jars directly. But, I'd try signing that compute jar as well and see if that resolves it for you.
As a secondary note, since your jar's manifest defines the main-class, instead of specifying the main class on the command line and the jar in the classpath, you can use the -jar switch to identify both. And if you add the compute.jar to the Manifest using the "Class-Path" attribute (and it can be specified as a relative path) you could then simply enter:
to run it. It keeps the command line simpler.
Let us know if that solves it. If not, perhaps someone else has some insight.
Joined: Jan 04, 2005
Thanks a lot for replying
It doesn't apply to RMI because the compute.jar is defined by the server, and then used by the client... and so i shouldnt need to sign it myself... I need the permissions from the server...
I realised that i was missing the codebase , it was always there i dont know how it disapepared
But now i'm having another trouble with permissions, but for this thread, it is solved
I was going to set the attribute, but when i first time attempted to change the manifest it said to me "invalid digest of message...", so i decided not to touch it again
Thanks a lot for your attempt very much appreciated.. HannaH [ July 22, 2008: Message edited by: H Melua ]