Actions
Bug #6567
open
Xerces parser fatal error handling
Status:
New
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2024-10-22
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
Xerces has a "org.apache.xerces.impl.XMLErrorReporter.CONTINUE_AFTER_FATAL_ERROR" feature. So by default one can control if the parser breaks or attempts to continue after a fatal error by setting this feature. But the Saxon implementation of the error handler net.sf.saxon.lib.StandardErrorHandler.fatalError(SAXParseException) always throws an error instead of just logging the error and relying on Xerces to break the parsing or not depending on its feature.
No data to display
Please register to edit this issue
Actions
.