-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More clues to where the error is located would be nice #52
Comments
Currently on vacation so only a quick answer.please try v5.0.0-b1 and give me feedback please. Thx |
Looks like the same to me using v5.0.0-b1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I enabled a flag in the Saxon runtime - maybe the makes things a bit better. |
Hi ! I'm using the following code to collect schematron errors: StreamSource source = new StreamSource(new StringInputStream(xml, StandardCharsets.UTF_8));
SchematronOutputType ouput = sch.applySchematronValidationToSVRL(source);
final ICommonsList<SVRLFailedAssert> failedAssertions = SVRLHelper.getAllFailedAssertions(ouput); Could you please provide an explanation or code snippet on how to read the "location" information ? |
Hi, the problem with the line numbers is mainly for the internal conversion of SCH to XSLT. In what exact context to do you expect line numbers?
In the created SVRL there is no option to get the line number of the respective XML - that's why you have the XPath expression. Please elaborate a bit more - thx |
Hi, here is what I want: I want the error lines number when I validate a XML content against a schematron. |
Unfortunately SVRL, the output language for Schematron validation, does not foresee the provision of line and column numbers for matching elements. So unfortunately there is no standard way to provide this - sorry |
Do we have another ways to have these line/column information ? |
Well I am not aware of a simple solution to do it. Evtl. you can use this method with some |
If the name of the file in question could be part of the stacktrace or the failed expression could be part of the trace it would be great. (The file 'schema.sch' is only the container for a lot of other files).
The text was updated successfully, but these errors were encountered: