XMLReporter only gets called for warnings, but not for non-fatal validation errors. This is incorrect as Stax specification and javadocs for XMLReporter; instead, reporter should be called for such errors.
This is important enough a problem to warrant getting backported to 3.2 series, since it makes it impossible to try non-disruptive validation of documents.
Description
(reported by Eduardo R Rodrigues)
XMLReporter only gets called for warnings, but not for non-fatal validation errors. This is incorrect as Stax specification and javadocs for XMLReporter; instead, reporter should be called for such errors.
This is important enough a problem to warrant getting backported to 3.2 series, since it makes it impossible to try non-disruptive validation of documents.
Fixed: DTDValidatorBase was not properly calling InputProblemReporter, but instead threw an exception. Additionally InputProblemReporter implementation had wrong logic in determining when to call XMLReporter.
Tatu Saloranta - 29/May/08 12:43 AM Fixed: DTDValidatorBase was not properly calling InputProblemReporter, but instead threw an exception. Additionally InputProblemReporter implementation had wrong logic in determining when to call XMLReporter.
Fixed in trunk and 3.2 branch.
Bug
Resolved
Major
XMLReporter not getting called for non-fatal validation errors
Fixed in trunk and 3.2 branch.