There are scenarios where fault details are not visible in the log and/or dropped entirely. An example of the latter case would be a situation where the exchange pattern is in-only and there's no fault handler registered for the reply. Here's what we need:

1) We should dump a nicely formatted error/fault message to the log when DEBUG logging is enabled. The message should provide summary info along with the complete content / stack trace of the error. Tomo's recent work with an exception -> string transformer should come in handy here.

2) The user should be able to hook a fault listener into an application and program their own logic to the error. This should be akin to a wire tap type of deal, so I wouldn't expect the code to influence processing of the message at all.