JDBCMailRepository contains several examples of exception handing similar to:
} catch (Exception me) {
throw new MessagingException("Exception while retrieving
mail: " + me.getMessage());
}
the downside with this approach is that information about the original
exception (including the stack trace) are lost. (i'm getting a null
pointer thrown but without a stack trace it's hard to know where the
problem lies.)
any reason why changing these to:
} catch (Exception me) {
getLogger().debug("XXX", me);
throw new MessagingException("Exception while retrieving mail: " +
me.getMessage(), me);
}
would be a bad idea?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
