One other thing to consider is that JDK1.4 has a version of Xalan in the rt.jar. I am not sure which version of the JDK1.4 you are using but FCS will contain Xalan D11. So the version on the class path may not be the version you are actually using as a result of it finding the classes in the JDK distribution first. You can get around this by placing xalan.jar in the endorsed lib directory of the JDK1.4. Alternatively, you can put xalan.jar in the bootclasspath of the JVM, that is if your JVM supports this option.
Tom Benjamin Riefenstahl wrote: > Hi Geert, > > "Geert Poels" <[EMAIL PROTECTED]> writes: > > To my surprise, I have a different output from the Xalan test using > > 1.3 or 1.4 with the same set of libraries in the classpath. > > Is it possible that you see stuff coming from the extensions directory > of the Java implementation? We had that problem with our J2EE > installation on Solaris. You may want to remove jar files containing > duplicate classes from the Java extensions directory. > > so long, benny > -- > Energis-ISION > Benjamin Riefenstahl > Harburger Schlossstrasse 1 > D-21079 Hamburg > > eMail: [EMAIL PROTECTED] > Web: http://www.energis-ision.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
