>Let me restate so I'm clear on what's going on, and hopefully others will >be too:
Close... At this time there really are some compile-time dependencies on Xerces. Most of them are in a class which is only used with Xerces, so if that class fails to compile it's ugly but isn't a problem for folks using other parsers. But there seem to be a few others. We should be able to fix the fomer with Still More Reflection (UGH!), and the latter by switching to JAXP, when someone can find time to work on that; it isn't my own top priority right now. I _think_ we don't have any run-time dependencies on Xerces, under normal operation. Summary: Compile with Xerces present, but you can probably run without it. Advice: If being able to compile without Xerces available is important, someone should submit a bugzilla request for enhancement to make sure we don't forget to address this. >All officially shipped Xalan builds will be compiled against >and include a copy of xerces.jar. Yep.
