In particular, changes that need to be adoipted include:
1. The parser and other libraries must not be part of the classes.zip file that holds the core Java library. I do think a parser and implementation should ship with the JDK. However, it should be able to be easily overridden or replaced by the end user. It should not be necessary to know the magic jre/lib/endorsed incantations just to choose a different parser. User parsers and implementations anywhere in the classpath should override the default parser.
2. It needs to be established that third parties such as the Apache project and the W3C can ship JAXP even if they are using a more recent version of an API such as SAX or DOM that adds additional methods and classes, and thus flunks the compatibility tests.
In brief, Sun needs to accept that SAX and DOM are third-party standards that are not and will not be defined in the JCP. They cannot be treated the same as core parts of the Java class library such as the Collections API. Sun can adopt these standards for use in the Java API, but it should recognize that it does not provide the only or the official definition of these APIs.
--
+-----------------------+------------------------+-------------------+ | Elliotte Rusty Harold | [EMAIL PROTECTED] | Writer/Programmer | +-----------------------+------------------------+-------------------+ | Processing XML with Java (Addison-Wesley, 2002) | | http://www.cafeconleche.org/books/xmljava | | http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA | +----------------------------------+---------------------------------+ | Read Cafe au Lait for Java News: http://www.cafeaulait.org/ | | Read Cafe con Leche for XML News: http://www.cafeconleche.org/ | +----------------------------------+---------------------------------+
