>I was just wondering if anyone from Xerces is tracking this?
Both Elena and Andy have shown interest; I don't know where it is on their priority lists. >Signficantly, the Xalan smoketest fails with Xerces2 and succeeds with >Xerces1. Xerces2 beta 3, when operated in incremental mode, is failing to deliver attributes; the startElement calls occur with non-null but empty attribute lists. (There have also been reports of failures in normal continuous-SAX mode; I haven't confirmed these.) I have to say here that the technique we're using to get Xerces2 to deliver incremental SAX rather than incremental XNI is on the hairy edge of the documented Xerces2 APIs, so this could be either a code failure or a documentation/usage failure. I really want to see SAX-level incremental parse encapsulated as a standard set of calls, as it was in Xerces1's experimental version, to reduce that set of risks. XNI is a fine idea (and some day Xalan may want to leverage it directly), but it shouldn't be a pre-req for incremental parsing, and incremental SAX should be available without Xerces2's current "magic" sequence of parser instantiation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
