On Thu, 24 Feb 2005, Steve Loughran <[EMAIL PROTECTED]> wrote: > What would happen if we run all of gump without xerces, that is, > against whatever JAXP is on the runtime?
The problem is not so much Xerces or Xalan but JAXP and DOM/SAX. Without using xml-commons' xml-apis.jar we are unable to build either Xerces or Xalan-J or XSLTC on JDK 1.5 or Kaffe because they don't implement the JAXP 1.3 set yet. Makes one wonder how different the Xerces and XSLTC versions in JDK 1.5 are compared to Apache's - and why the stuff hasn't been ported back, yet. But I digress. The JAXP 1.3 and in particular DOM 3 changes ripple through the rest of the Gump set. This like jdom, dom4j, jaxen, cocoon all wouldn't build and we end up with a lot of "pre-req failed" projects. For JDK 1.4 we'd have not that many problems, but there may be a few builds that require a parser supporting XML Schema, which Crimson does not. The only reasonable alternative to our current setup would be JAXP 1.2 set of APIs but using the native parser transformer of JDK 1.5/Kaffe. This currently fails because the xml-commons' API's factories default to Xerces and Xalan. It should be possible to play with system properties to fix that. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
