During development of uno-choice 2.0 I was surprised that the fallback script did not get the exception, or even just the message, into its context.
As noted in SECURITY-470:
- When a script fails the exception is logged on FINEST and not made available (not even it's message) to the fallback script. This makes investigating causes for problems unnecessarily annoying.
I am requesting that at least ex.getMessage() be added to a fallback script's context. Possibly also the exception type, and/or stack trace. Not sure whether individual variables are easier than just passing on the exception object, but something is needed.