Testing just now with webstart on windows with JDK version 1.5 I came across an error where webstart refused to launch my application claiming "found unsigned entry in resource". In other words, it claimed that my jar file was not properly signed. But the jar file IS properly signed, and worked fine with
java 1.4.
A little research on forum.java.sun showed that others have had this problem and that the solution is simply to try again. After reloading the jnlp file three times, the problem went away.
I don't like the idea that my customers may have to do this. They would probably assume there was an error in our application, not an error in WebStart, and might not be willing to re-try three times.
Anyone else seen this problem?
Know any work-arounds? Maybe I need to use a jdk1.5 jarsigner rather than the jdk1.4 jarsigner?