We have a subclass of ThrowableProxyConverter here, where we used to override throwableProxyToString to add this. Since 1.1.0, it got a bit harder to do this because some package-protected methods were changed.
If I were to contribute this, what solution would the Logback developers like to see?
SQLException in ThrowableProxyConverter.recursiveAppend could be another special case (like suppressed exceptions).
Or there could be a new protected Iterable<IThrowableProxy> getAdditionalExceptions(IThrowableProxy tp), where subclasses could add any additional exceptions they want. Any returned values would be handled using recursiveAppend (with a different prefix).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
We have a subclass of ThrowableProxyConverter here, where we used to override throwableProxyToString to add this. Since 1.1.0, it got a bit harder to do this because some package-protected methods were changed.
If I were to contribute this, what solution would the Logback developers like to see?
SQLException in ThrowableProxyConverter.recursiveAppend could be another special case (like suppressed exceptions).
Or there could be a new protected Iterable<IThrowableProxy> getAdditionalExceptions(IThrowableProxy tp), where subclasses could add any additional exceptions they want. Any returned values would be handled using recursiveAppend (with a different prefix).