DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5272>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5272 Problems using Xerces2 beta 3 incremental [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|SAX |org.apache.xml.dtm Product|Xerces2-J |XalanJ2 Version|2.0.0 [beta 3] |2.2.x ------- Additional Comments From [EMAIL PROTECTED] 2001-12-12 13:07 ------- Thought I have no idea what axes113 or lre13 mean, I managed to reproduce the problem using foo.xml and foo.xsl that come with Xalan binary distribution. But I only see incorrect output when -INCREMENTAL is set, that is, I couldn't reproduce what Tom Amiro described. Here is what I think causes the problem: in IncrementalSAXSource_Xerces (package org.apache.xml.dtm.ref), if the underlying xml parser is xerces-2, first a pull parser configuration (fPullParserConfig) is created, then a sax parser (fIncrementalParser) is created based on this configuration. When an xml file is parsed in the pull-parsing mode, the parse(boolean) method is called on the configuration (not on the sax parser, I guess because it doesn't have a pull-parse method). The result is that the reset() method of the sax parser never gets a chance to be called. If I insert fIncrementalParser.reset(); before fConfigSetInput.invoke(fPullParserConfig,parmsa); then everything works fine. I'm send this bug back to Xalan. But it might be an enhancement for Xerces to provide pull-parse method on XMLReader interface. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
