"Swanson, Brion" wrote: > 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?
Xalan2 should be able to use the JAXP parser. However... I think they might try do some tricks if they detect that the JAXP parser is the Xerces parser. And since the Xerces2 DOMParser and SAXParser classes have the same names, it has no way of telling the difference. Therefore, it *may* be trying its tricks and not finding the right classes. Have you tried running it with only the Xalan2 xalan.jar file and *not* adding the xerces.jar that comes with Xalan2? Or is that what's causing the problem to begin with? In that case, you may have to do a little trick by changing the META-INF/services files. Perhaps the Xalan folks can help you more in fixing this problem. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
