A few questions about signing JARs for Web start

I'm still a bit new to all this, so just want to clear a few things up.

I'm currently trying to publish an application using Web start, so i know I have to sign all the JARs, as it needs to do some writing to the hard drive.

1. I have my main JAR file, and then two "third party" JAR files in the /lib subfolder, I take it I need to sign those two as well, does it matter that I don't have the .class file for those two, as I didn't write them?

2. I'm running the JARSIGNER program with exactly the same command line apart from the filename of the .jar file, is that correct? or do I need a different certificate for each .jar file?

Just can't seem to get all three signed, Web start says one different one isn't signed each time I try it out.

3. When signing, does it add something to the end of the JAR file itself? as I can't see any extra files created.

[902 byte] By [forgeuka] at [2007-11-27 5:41:41]
# 1

Signing adds entries in the mainifest, not in the main file list in the jar file.

You can sign third party jar files, but it is not advisable. An alternative is to put third party jars in a seperate extension jnlp file, if they need all-permissions, you can get the third party jars already signed by whoever supplied them. If not, you do not need to request all-permissions in the extension jnlp file, and that part of the code will be run in the secure sandbox.

/Andy

dietz333a at 2007-7-12 15:19:28 > top of Java-index,Desktop,Deploying...
# 2
I solved similar problems by repackaging the third party jars in one jar by using the jar command. Then I used the same key for signing all jars of my web start application. I had to delete some signing information of the third party jars in the common manifest directory.
Holger_Burbacha at 2007-7-12 15:19:29 > top of Java-index,Desktop,Deploying...