That would be nice. But what kind of exceptions are you referring to? Are they really "Exceptions" or you are using exceptions as part of control flows? (which should be avoided). Currently, Rule-Connector-Java.Invoke captures ActivityTerminationException, PRAppRuntimeException and PRRuntimeException and rethrow them.
Indeed, the transition does catch the error, which is what we're using.
But the stacktrace has already been thrown.
Like I said, if we have time, I'd just have the team to rewrite this to call Java directly. I'd be happy to use the macro-ability of activity methods, but only if they can provide us with the same measure of control as in Java.