Jeff Turner wrote: > > One remaining question: will it be possible for an application to > override the default parser (crimson I think), or when 1.4 is released, > are we stuck with that parser and it's bugs?
JDK 1.4 contains the JAXP 1.1 API along with the JAXP reference implementation (RI) which includes crimson 1.1.3 and xalan D11. JAXP 1.1 contains a pluggability feature. As Shane mentions you can place any JAXP compatible implementation like Xerces 2 or saxon on the CLASSPATH and it should all work. (BTW, there are other ways to override the implementation in JDK 1.4 as well mentioned in the spec, see http://xml.apache.org/~edwingo/jaxp-faq.html for pointers to more info.) > So far, when it comes to standards, Microsoft have "embrace and extend", > and Sun have "embrace and inadvertently hold back". I wish they'd leave > XML out of the JDK, but failing that, I hope (and would like > confirmation from this group) that they haven't killed the advancement > of DOM and SAX in Java. The endorsed standard mechanism was designed for this and it is based on the -Xbootclasspath mechanism that Dims mentions. -Edwin --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
