Project

Profile

Help

Bug #2592

closed

XSD validation regular error events treated as fatal error events

Added by Yitzhak Khabinsky almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
High
Category:
-
Sprint/Milestone:
-
Start date:
2016-01-19
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
9.7
Fix Committed on Branch:
9.7
Fixed in Maintenance Release:
Platforms:

Description

It seems that a new bug was introduced in the 9.7.0.2 version while fixing the following bugs:

• -1 value for both line and position values in schema errors

From https://saxonica.plan.io/issues/2515

• Schema validation: Fatal errors handled differently

From https://saxonica.plan.io/issues/2516

The XSD validation error events are completely gone. For the same XML/XSD file pair, XSD validation regular errors are handled now as fatal errors. Any XSD validation error is a fatal error now.

The attachment contains a use case to reproduce it.

Three RECEIPT files show progression for the following Saxon versions:

  1. SAXON 9.6.0.7, EE-Java

a. correct behavior

  1. SAXON 9.7.0.1, EE-Java

a. XSD 1.0 errors produce correct line and position values

b. XSD 1.1 asserts, error events produce line=”-1” and position=”-1”

  1. SAXON 9.7.0.2, EE-Java

a. XSD 1.0 errors became fatal errors and produce correct line and position values.

b. XSD 1.1 asserts, error events became fatal events and produce correct line and position values, though different values comparing with 9.6.0.7 version values.

IMHO, the logic in the MyErrorListener.java file in the attachment should be applied to resolve the new bug.

  • All 3 XSD validation event are legit:
  • Warning
  • Error
  • Fatal
  • 2 global counters:
  • Warning event counter counts warning events
  • Error counter counts both (error + fatal error)

Files

Saxon9.7.0.2_vs_EarlierVersions.zip (31.6 KB) Saxon9.7.0.2_vs_EarlierVersions.zip Yitzhak Khabinsky, 2016-01-19 21:33

Please register to edit this issue

Also available in: Atom PDF