> 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.
Yeah, I recall something like that from a previous thread [1]. > 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'd say that what's happening is: - If "xalan-2.6.0.jar" comes first, Java tries to resolve the "xercesImpl.jar" dependency by using the internal provided one. This could explain the issue, as the "xercesImpl.jar" shipped is apparently pretty old (please refer to the previous thread); - If "xercesImpl.jar" comes first, probably Java uses the "overridden" Jar instead of the internally provided. This could explain why this would work; - Explicitly removing the entries can be causing Java to wait for the whole Jar list in order to resolve. Either way, I couldn't find official information supporting the Jar/class resolution behavior (from a quick search, that is). Hope this helps, Helder Magalhães [1] http://www.nabble.com/why-rename-xercesImpl.jar-to-xerces_2_5_0.jar--td20034830.html#a20034830 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
