Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.9
-
None
-
Patch available
Description
line 448 eats the chain of exceptions, which is bad for finding bugs and misconfiguration.
It should better read:
} catch (MessagingException me) {
throw me;
or
} catch (MessagingException me) {
throw me; // new MessagingException(me.getMessage(),me);
or be eliminated all together, following the principle, if you can't do anything about an exception and don't need to aggregate it, because of API design, don't catch it in the first place!
It should better read:
} catch (MessagingException me) {
throw me;
or
} catch (MessagingException me) {
throw me; // new MessagingException(me.getMessage(),me);
or be eliminated all together, following the principle, if you can't do anything about an exception and don't need to aggregate it, because of API design, don't catch it in the first place!