That is fine.. Not a big enought deal to argue about it. I will make
the change.
Kevin
jon * wrote:
>
> on 2/3/00 10:13 PM, Kevin A. Burton <[EMAIL PROTECTED]> wrote:
>
> > jon * wrote:
> >>
> >>> catch ( ClassNotFoundException e )
> >>> {
> >>> + e.printStackTrace();
> >>> throw new Exception ( "Requested Screen not found: " + name );
> >>> }
> >>> return screen;
> >>
> >> Kevin,
> >>
> >> I'm -1 on this change because it is something that should be caught higher
> >> up. You should catch that exception somewhere else...because it has a "nice"
> >> error message in it. If you want to print a stack trace from that exception
> >> later on, then that is fine
> >
> > No... it really isn't. Yes. It is true you get a stack trace but the
> > trace only goes up to the point where your did "throw new Exception".
<snip>
--
Kevin A Burton
Senior Software Engineer
Kendara Inc
http://www.kendara.com
Mobile: 408-910-6145
Linux - The revolution will NOT be televised
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
