Maybe given that we have to catch Exception in the mailet container no matter what (you can't have runtime exceptions breaking processors), we should remove MailetException and change the API to "throws Exception".
IMO we do want to distingush between two cases,
Yeah, but how? MessagingException includes exceptions that do not relate to underlying problems. For example, if I have my mailet's init construct an InternetAddressed based on some configuration parameter, that will throw a MessagingException.
What I think is probably bad is for both cases to be an instance of (and castable to) the same exception, particularly if we think that developers should be handling them in different ways.
How would you have developers handle these differently? Ideally I'd rather not have to require the developers to worry about underlying store exceptions, but to remove that worry, we prevent us from being able to handle much at all.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
