---- you [EMAIL PROTECTED] wrote ---- > There are currently some compile-time dependencies. There shouldn't be any > runtime dependencies.
Let me restate so I'm clear on what's going on, and hopefully others will be too: In Xalan There are currently some optional compile-time dependencies. There aren't any fundamental runtime dependencies. However *if* xalan.jar is compiled with xerces.jar present (1.4.+ or 2.0.0beta3) *and* is run with xerces.jar present, *then* some nifty *optional* features are available. (Basically, if you use Xerces, Joe and Scott have some nifty parser optimizations that are custom to Xerces; if you use another parser, we fall back on defaults). All officially shipped Xalan builds will be compiled against and include a copy of xerces.jar. Sound good? We should probably make sure the community understands this; it will also be a potential issue for the upcoming JAXP releases that may use Xalan with Crimson (which was the JAXP reference parser, last I checked) or future JDK releases. Oh, for Xalan developers curious about switching parsers, look in xml-xalan/java/build.bat for PARSER_JAR (I don't know if I ever updated the build.sh with equivalents) and build.xml for parser.jar.name While I'd definitely like to get all references cleaned up to use proper reflection (so it doesn't matter which parser we compile with/run with in any combo), I don't have a spare Round Tuit, and basic conformance tests seem happy to run or compile with either Crimson or Xerces, so I'm taking Joe's word that it works. - Shane
