> Currently we're stuck with this problem, so we have to pick a global > compromise between verbosity and lose of critical information. Until this > problem can be fixed, at the least exceptions thrown by a mailet should be > considered a warning, if not an error. True, some of them > aren't, but we're > still stuck with a compromise, and better to assume that an exception is > important than to discard it.
As far as I'm concerned the logging of mailets should be an issue for mailet developers, developers are free to use commons logging or anything else in their mailets, as is the case in the servlet API. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
