Description Jens Borrmann 2010-09-28 08:47:08 EDT

Build Identifier: 1.3.0.20100615-1704

http://www.eclipse.org/forums/index.php?t=msg&th=41660&start=0& 

rwt.testfixture cannot be used in combination with the rwt-bundle that is contained in a RAP release. The reason is that the release jars are signed and so cannot be mixed with unsigned jars. 

java.lang.SecurityException: class "org.eclipse.rwt.Fixture"'s signer
information does not match signer information of other classes in the
same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:776)
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:488)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at java.security.SecureClassLoader.defineClass
(SecureClassLoader.java:124)

The three workarounds proposed in the forum thread are in my opinion not sufficient:
1) Using "normal" bundles from CVS for testing: We have to make sure, that the same code is run in our tests that will be packaged and shipped to our customers. _I_ know that this can be ensured via CVS tags, but this argument is usually not understood by non-technical people.
2) Removing the signing information from the production bundles: As discussed in 1) in this case I would have to use the unsigned jars in production, too. This is only a minor problem - most libraries we use are not published with signing information. The other drawback is that this manipulation has to be repeated with every RAP update.
3) Turning off checks via command line: I am not aware of such a parameter. Even if it existed I would not want to mask real problems in other areas of my system by using such a switch. Else I might see those problems in production.

Reproducible: Always