On Tuesday, 12/18/2001 at 11:30 EST, [EMAIL PROTECTED] wrote: > Hi Joseph. Have you tried running with the split jar file (i.e., not using > the oldXerces distro)?
I wanted to try the supposed plug-in replacement first as a sanity-check. Trying it that way now, using our PARSER_JAR environment variable to override and point to both the new jars instead of the old one . The old build of Xalan was _not_ compatable with the new jarfiles (complaints about not finding the JAXP parser). I had to recompile Xalan from scratch, which is going to be a maintainance/distribution problem unless it can be corrected -- it would force us to ship two different ready-to-run builds, which I don't think we'd be happy with. Note that this change, whatever it is, wasn't present in the single-jarfile version of Xerces2b4. After rebuilding Xalan to get around this problem and running its smoketest: results look identical to those obtained from the single-jarfile version. General comment: Factoring out the standards is a fine idea -- Xalan also did so, with its xml-apis.jar file -- but unless Apache can reach a consensus on a _common_ factoring, the idea simply does not achieve its goals. I'm not saying that xml-apis.jar is necessarily right and xmlParserAPIs.jar is necessarily wrong, but the two should agree on what is and isn't an XML API and have, at worst, equivalent content. (I would really like to see a _single_ xml APIs jarfile for all of Apache, to guarantee we're all speaking the same language -- with local overrides if necessary for prototype APIs, which could be placed earlier on the classpath if and only if there's an intent to use the prototypes.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
