In SAX or DOM mode, Xalan should currently be able to handle any 
namespace-aware parser.

If you're letting us instantiate the parser, we will attempt (via 
reflection) to take advantage of some of Xerces' internal features, but if 
we don't find Xerces2 we should fall back on Xerces1, and if we can't 
recognize it as Xerces1 we should fall back on JAXP and SAX.

(At some point, I think we ought to rip out the explicit support for 
Xerces1 -- I know I don't intend to put a lot of work into ongoing support 
for that code, and it's a distraction when trying to maintain the Xerces2 
support. We can always fall back on generic SAX.)


______________________________________
Joe Kesselman  / IBM Research

Reply via email to