committed
On 8/2/07, norman <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, den 01.08.2007, 20:32 +0000 schrieb Robert Burrell Donkin:
> > 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
>
> +1
>
> Norman
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
