Java SE (Java Platform, Standard Edition)

Iam a little unsure about the way in which web start checks signed .jar's

I have a verisign certificate which needs to be renewed shortly as it is only valid for a year, the problem is not the cost of renewing the certificate but, what about already deployed .jars to our customers intranets.

Do we have to resign all the deployed .jars when we recive the new ID, as this will be a deployment nightmare for us if we have to do this every year.

Or is there another soloution, in the mail we recived from verisign it says that already signed .jars if timestamped do not expire after the expiration date.

Is this correct, that if .jar's are time stamped that they continue to work ?

Tested so far:
I have tried adjusting the bios date on a PC a few months after the certificates expiry date, but it seems to work fine, is it because the jars are time stamped ? as I dont think I have time stamped them, unless this is done by default by the jarsigner.

Can anyone explain, as I dont understand how web start handles signed jars.

Thanks and regards

Gary