IllegalStateException is thrown when validating invalid date value about validator HOT 7 CLOSED

Yes, at least for your environment and test file, version 1.1.0 was working correctly. But you can easily have a scenario where schema validation works and schematron validation will fail with that same error in 1.1.0 too.

So these are bugs:

1. a regression introduced in 1.1.1 that the schematron validation is started when schema validation fails

2. a bug in 1.1.x that processing errors while validating with schematron (and also when validation with schema) are not properly progagated to the callee via Result-object.

This is fixed in master and branch-1.1.x. I'll do some testing in the next few days before pushing a new release. Thanks for reporting!

from validator.

the error report indicates, that the Version 1.1.0 is failing at schema validation step and stopping further processing while 1.1.2 is proceeding after this and then just fails on schematron step.

There was bug in 1.1.0 regarding malformed XML or garbage, that has been fixed in 1.1.1. Unfortunately this results in this error. I'll fix this

from validator.

Hi,

thx for reporting.

However, this is not issue of the validator itself. It is related to changed validation rules as configured in validator-configuration-xrechnung_1.2.2. Even more precisely Error evaluating (fn:exists(...) and fn:exists(...) and xs:date(EndDate) ge xs:date(StartDate) or fn:empty(...) or fn:empty(...)) in xsl:when/@test on line 2036 column 188 of EN16931-UBL-validation.xsl: tells me, it is a validation rule of https://github.com/ConnectingEurope/eInvoicing-EN16931 which we just integrate in our validator-configuration-xrechnung.

I will try to ask them that they write this rule more robust and with better error messages.

from validator.

Thank you for a quick response.
Using the configuration version 1.2.2_2019-12-30 and validationtool-1.1.0 I don't get the exception. It occurs just after updating the validation tool to version 1.1.2.

from validator.

Ah ok, then we might have two issues at the same time! We will investigate this too.

from validator.

@apenski does it seem like a bug in 1.1.0 ?

from validator.

I assume that behvaiour of the version 1.1.0 is actually correct, is it true? Two schema violations make sense for me :) Moreover thank you for taking care of the problem. I appreciate it.

from validator.