Java 1.5.0_04 apparently still has this fatal webstart bug.
1. make a few jars
2. sign each of them individually
3. use all-permissions
4. access the JNLP
1. Java downloads the JAR's
2. Java claims that PART of your Jar file is unsigned. Obviously, this is *impossible* - you either signed the file or you didn't.
3. You break down and weep at how crap webstart's implementation is.
1. Only one google hit on this problem, and the solution was: "I read that filenames with length 131 or 132 chars cause JWS to throw-up. Turns out that out of the 1000+ file I have in this particular jar 2 files have names that are exactly 132 characters. Increasing those filenames by just one character has fixed the problem !"
I've checked there aren't any files with names anywhere near that long.
Since this is not the first, 2nd, 3rd, or even the 5th time I've encountered similar bugs with Sun's JWS + signing (just random errros that are out-of-touch with reality and have no apparent cause and no apparent fix) I'm edging very close to giving up on it entirely.