not if JAXP is used. JAXP by-passes the classpath rule and instead takes the first jar in the classpath that contains the META-INF/services/JAXP-specific-files. however older versions up to, but not including 1.4.3 did not contain the proper files, tho Crimson does. i'm not sure if Xerces2 has these files or not as i'm still using the old Xerces.
-----Original Message----- From: Swanson, Brion [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2001 6:01 AM To: '[EMAIL PROTECTED]' Subject: RE: Help, Xerces 2.0 beta install problem I'm running this under SunOS 5.7 with 4 CPUs and plenty of memory and storage (it used to be a production machine - possibly still is for old products). The only thing I can find in my classpath that might contains an old Xerces version is Xalan2. However, that appears after my Xerces2 JAR, so it should check the Xerces2 classes before it reaches the Xerces1 classes bundled with Xalan, correct? -------------- Brion Swanson -----Original Message----- From: Andy Clark [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2001 2:27 AM To: [EMAIL PROTECTED] Subject: Re: Help, Xerces 2.0 beta install problem What kind of environment are you running this under? Is there any possible way that it could be using the old Xerces JAR file? I don't see anything in your code that would be causing the problem you are seeing. As long as you stick with using the standard XML interface (DOM, SAX, JAXP, etc), you should be shielded from any implementation changes. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
