Hello, we think it is pretty simple and straight forward to throw exceptions in custom workflow logic (like listeners, service tasks, script tasks) when ever there is a problem, of which the current user can be informed with a very specific message. For instance, that could be caused by validation of form data. The good thing about the exception is, that the workflow transaction is rolled back and everthing is fine, the user can now try again because we also roll back all of our transactions on any exception. But this has only one downside: everytime the user tries to submit the form (e.g.), a stack trace is printed and/or logged in file, which is totally unnecessary. Can I somehow influence the handling of that exceptions thrown within workflow logic? Best would be: the trace only gets printed if the nested exception (the exception we threw and is nested in an ActivitiException) is not of a certain custom type. Do you have any suggestions? Thank you!
