[
https://issues.apache.org/jira/browse/XERCESC-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1643:
-------------------------------------
Fix Version/s: 3.1.0
It would be good to verify if this is still an issue in 3.0.1 and fix it for
3.1.0 if that's the case. David, will you be able to look into this, seeing
that you are the Assignee for this bug?
> DOM Parsers do not cleanup parseInProgress state after fatal exception
> ----------------------------------------------------------------------
>
> Key: XERCESC-1643
> URL: https://issues.apache.org/jira/browse/XERCESC-1643
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
> Affects Versions: 2.7.0
> Reporter: Jason E. Stewart
> Assignee: David Bertoni
> Fix For: 3.1.0
>
>
> Both DOM parsers (DOMLSParser, XercesDOMParser) appear to not properly reset
> their state after a fatal error, and if you attempt to call parse() again,
> they throw a parse-in-progress exception.
> SAX and SAX2XMLReader appear to handle the cleanup properly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
