Challenges with Separating Error Messages and Exceptions in Saxon Library

[volodya-lombrozo]

Not so long ago, we encountered the following problem: objectionary/eo#2114, which was caused by strange behaviour of the <message> element. The issue lies in the separation of the exception caused by net.sf.saxon.expr.instruct.TerminationException and the message produced by the <message> element. In the logs, they appear separately: the <message> body is printed before the java exception is thrown, and quite often, it's difficult to connect them to each other.

Expected behavior: The error message (<message> body) should be included in the java exception message. In other words, when the java exception is thrown, we want to see the original reason that was added to the <message> body.

Currently, we have to search for them in the logs and attempt to connect them.
It seems that this is a well-known issue in the Saxon library:

• Stack Overflow: https://stackoverflow.com/questions/27522994/xsltmessage-in-saxon-where-is-the-message
• Saxonica documentation: https://www.saxonica.com/documentation9.5/xsl-elements/message.html"

[yegor256]

@volodya-lombrozo it's a known problem, but thanks for reporting it. If you are willing to contribute with a PR, you are welcome. Otherwise, I don't know how to fix it :( Let's keep it open.