The developers in my project are having an odd problem with Batik 1.7, namely that it seems to matter in what order the JARs shipped with Batik are given on the classpath. Here's what happens:
First, we renamed xerces_2_5_0.jar to xercesImpl.jar (as it was named upstream, I think) for reasons that I no longer recall. If we put xalan-2.6.0.jar before xercesImpl.jar, we get a NoClassDefFoundError when trying to load PSVIProvider (from org.apache.xerces.imp.xs.psvi.PSVIProvier), but if we have them in the other order than it works fine. What I've been able to determine is that removing the entries in the xalan-2.6.0.jar's INDEX.LIST which refer to external jars (in this case, xercesImpl.jar and xml-apis.jar) also solves the problem. I'm not really sure what's going on with this. Is this a problem with the way we're using the JARs? Is this a problem with the way that Batik ships the JARs? -- J. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
