> Here is my understanding: the intent of having the signature tests is as > a partial solution to enforcing spec conformance. For example, there is > a J2EE 1.3 spec and several implementations from various vendors like > BEA, IBM, and the reference implementation (RI), that attempt to conform > to it. The goal is to allow an app component, call it C, that uses the > J2EE 1.3 API to be able to run in any 1.3 compatible implementation.
Seems like that goal calls for testing components against API specs, doing things like "may only use methods in the 1.3 API spec", rather than testing platforms! Though testing platforms is easier (there aren't so many of them to test) and is already done for many other reasons. It's good to know that JDK 1.4 systems can just drop "sax.jar" into $JAVA_HOME/jre/lib/endorsed and get the ability to run software that needs more current APIs. I added an entry to the SAX FAQ on that topic. Presumably that'll work for J2EE as well as J2SE. - Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
