Using doc-available()
correctly with invalid resource with false()
result throws Java IO exception
#219
Labels
bug
Something isn't working
Describe the bug
When purposefully using the
doc-available()
Metapath function with an invalid path in a constrainttest()
, the current stable version of the library throws an underlying Java IO exception that the invalid location cannot be resolved and access. That is intentionally the nature of using this function as a precondition check. The processor cannot emit a test message as the stack trace halts execution before that.Who is the bug affecting
Developers writing software processing constraints on document instances or developers maintaining the constraints themselves.
How do we replicate this issue
validate-content
command.Expected behavior (i.e. solution)
Only a Metapath evaluation to
false()
and the constraint message is properly displayed in the case of such constraint violations.Other comments
No response
The text was updated successfully, but these errors were encountered: