Hi I noticed in a few of the custom Message implementations, the getThrowable method always returns null (take for reference MapMessage). In code such as the slf4j bridge or even AbstractLogger there's explicit calls to this method. So the fact that the throwable is always null seems odd to me. If I were to subclass MapMessage to add support for actual Throwable, would there be any downside?
John --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
