Bug #2386: Validation errors missing column number - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #2386

closed

Validation errors missing column number

Added by Michael Kay almost 9 years ago. Updated over 8 years ago.

Status:

Closed

Priority:

Normal

Assignee:

O'Neil Delpratt

Category:

Diagnostics

Sprint/Milestone:

9.6.0.6

Start date:

2015-05-30

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

9.6

Fix Committed on Branch:

9.6

Fixed in Maintenance Release:

9.6.0.6

Platforms:

Description

In some cases (unspecified) validation of a source document against a schema produces validation error messages with a line number but no column number identifying the location of the error.

Actions

Copy link

Updated by Michael Kay almost 9 years ago

In some cases (unspecified) the following change to ExpressionLocation.getSourceLocator() fixes the problem:

public static SourceLocator getSourceLocator(int locationId, LocationProvider locationProvider) {
        if (locationProvider instanceof SourceLocator) {
            // this is typically true when validating input documents
            return (SourceLocator) locationProvider;
        } else if (locationId == -1) {
            return null;
        } else {
            ExpressionLocation loc = new ExpressionLocation();
            loc.setLineNumber(locationProvider.getLineNumber(locationId));
            // following line added...
            loc.setColumnNumber(locationProvider.getColumnNumber(locationId));
            loc.setSystemId(locationProvider.getSystemId(locationId));
            return loc;
        }
    }

The change has been applied to 9.7 but needs more testing before applying it to 9.6.

Actions

Copy link

Updated by Michael Kay almost 9 years ago

Status changed from New to Resolved
Found in version set to 9.6

The above change adds column numbers to the error messages for a straightforward command-line validation run, so I have committed it on the 9.6 branch.

Actions

Copy link