Mix of signed and unsigned jars in JAXB 2.0 EA
There are a few jars that are needed to run JAXB 2.0 code. All of them but one are unsigned. The remaining one, activation.jar is signed by Sun. This poses some problems for Web Start applications that need access privileges.  describes the way to handle the problems.
Is there some mention of this fact in JAXB 2.0 release notes or developer guide?