On Mon, 05 Jul 2010 14:36:28 -0400, Michael Glavassevich wrote: > "Holger Hoffstaette" <[email protected]> wrote on > 06/10/2010 11:09:07 PM: >> Turns out that after fixing that it happily explodes because >> DeferredDocumentImpl pulls in ElementTraversal - which doesn't exist in >> the JDK - and it's all downhill from there. I thought I'd get by without >> the new SAX/DOM APIs but apparently not..at least that explains the >> somewhat weird dependencies in SpringSource's xml-commons bundle. > > I'm not familiar with the issue. What would need to be done in xml-commons > and why?
I (probably) "only" would have needed to bundle xml-commons with a proper version and then import them as well, so that xerces does not see the JDK interfaces. However that seems fraught with problems because of the existing class loading, JAXP activation etc. in xml-apis. Other than that..the entire trifecta of xml-apis/xerces/xalan and their cross-dependencies is hopeless in their current state. Coupling JAXP activation and SAX/DOM interfaces, xalan depending on internal xerces classes.. I pretty much lost interest after checking out all three projects and getting them into eclipse. -h --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
