You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have seen that when there is a compilation fatal error in the XSLT, for example using Saxon that does not report errors directly, the default ErrorListener that Spring adds just throws the exception and does not log the error. The exception is wrapped later on and the compilation error message is then lost.
We'll add our own ErrorListener to log the fatal errors before throwing the exception up the chain.
The text was updated successfully, but these errors were encountered:
We have seen that when there is a compilation fatal error in the XSLT, for example using Saxon that does not report errors directly, the default ErrorListener that Spring adds just throws the exception and does not log the error. The exception is wrapped later on and the compilation error message is then lost.
We'll add our own ErrorListener to log the fatal errors before throwing the exception up the chain.
The text was updated successfully, but these errors were encountered: