This is in regards to my issue raised in the "[Xerces2] Design Decisions (LONG)" thread. Specifically, the last point: [4] Remove Dependence on SAX Unless I hear a public outcry, I'm going to start removing the direct dependence on SAX interfaces and classes from XNI. For the most part people so far have not cared or have thought it was a good idea. (Except perhaps Elena... ;) By removing the dependence we have a truly independent framework of interfaces and classes upon which *any* kind of XML parser can be written and plugged together. I consider this a good thing. And users won't even know the difference. If they use the DOMParser directly or call the DOM L3 load interfaces, a wrapper class will hide the underlying interfaces. The same is true for users of the SAXParser or the XMLReaderFactory and of users creating DOM and SAX parsers from the JAXP interfaces. It's important to note that removing dependence on SAX does NOT mean that we're removing support for SAX parsing from Xerces-J. XNI is an internal (or "native") set of interfaces and exists to allow us to build (and then properly layer) parser components, configurations, and parsers. Going once... Going twice... -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
