Yup, this is a feature of JAXP's FactoryFinder classes. Since the JAXP stuff is pluggable (i.e. the TransformerFactory interface will find you an implementation, allowing you to plug in new implementations without recompiling your code), they left several ways to define which implementation gets loaded each time. I don't remember if the JAXP spec details the decision tree, but javax.xml.transform.FactoryFinder comments it.
If a system property is set, it uses that; otherwise it searches the classpath in order for .jars that have the proper META-INF/services files - and if the Oracle .jar is first in the classpath, then you'll get the Oracle implementation. There's also a lookup for a jaxp.properties file and a final hardcoded fallback name. ===== - Shane <eof aka="mailto:[EMAIL PROTECTED]" .sig="Du sublime au ridicule il n'y a qu'un pas." /> __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
