Stephane Hillion wrote: > >> It turns out the essence of the problem can be stated "can batik be used >> programmatically from within an application which makes use of xerces2"? >> [...] >> Apparently if I run using the -jar option it works. But when I construct >> my classpath and happen to have xml-api.jar from xml-commons and >> xml-xerces2 xercesImpl.jar and xmlParserAPIs.jar from xerces2 earlier in >> the classpath, I get the error above. > > xml-commons' SAX version is newer than the one used by crimson. Perhaps the > problem has something to do with that.
The conflict appears to be between batik-ext.jar and xml-apis.jar http://gump.covalent.net/jars/2002-04-02/xml-commons/xml-apis.jar http://gump.covalent.net/jars/2002-04-02/xml-batik/batik-ext.jar If every project has their own private version of the various org.w3c org.xml interfaces only invites integration problems such as these. This will likely also cause problems with future versions of the JDK. Is there any hope that batik can cooperate with the xml-commons initiative? - Sam Ruby --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
