I'm... Ahem... Using an older version of the parser. Based on your comments, I grabbed the latest version of the sources and saw the code you showed below. I rolled the fix into the source for the version I'm on and it works fine. With the fix in place I removed my calls to reset and everything's working fine.
Thanks for your help. --Doug > -----Original Message----- > From: Glenn Marcy [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 08, 2001 9:58 PM > To: [EMAIL PROTECTED] > Subject: Re: Reusing parser instances > > > > >Andy writes: > >>"Smith, Doug" wrote: > >> I've been pooling and reusing Xerces-J 1.x parser instances, using > >>the > >> reset() method on SAXParser. Everything works fine until a content > > >You should not call reset() directly. > > Actually, calling reset() is fine. What I cannot understand > is how you can ever see fParseInProgress set to true when the > end of parse() > is: > > finally { > fParseInProgress = false; > } > > I am hesitant to start resetting state in the parser to avoid > failures of language runtime guarantees. Is there anything > about your environment that could possibly explain this ? > The only think I could think of would be if you were calling > parseSome() instead of parse(). > > More information will be needed to help track this down... > > -Glenn > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
