Yep. If theres one thing I hate its spending hours on a friday night
tracing through some other developers code to find why something in the
api they expose doesnt work and eventually coming to:
catch(Throwable t)
{
return null;
}
deep in the bowels of it and knowing that I cant even fix i
Koon Yue Lam wrote:
Hi !!
I agree with all of you but still have a question. If my application
is divided into a few layers, say:
Web <---> BizDelegate --- <---> EJB
|__<--> DAO / server side program
My practice is catch all SQLException in DAO(s), but never thro
Hi !!
I agree with all of you but still have a question. If my application
is divided into a few layers, say:
Web <---> BizDelegate --- <---> EJB
|__<--> DAO / server side program
My practice is catch all SQLException in DAO(s), but never throws
excepion from m
Dan,
Thanks for sharing your pain. You should check out Jalopy on SourceForge. It
is a code formatter and code inspector. It allows you to format your java
code according to your organization's conventions and also inspect it for
some of the items in Joshua Bloch's Effective Java book. The code ins
I usually wack log and assert false; if there is nothing better to do
with it at the time. In situtations where you know an exception can
never be thrown, I still would leave in at least this.
Of course this view also comes I'm sure from being in your position
before now. I don't recall but it's
> -Original Message-
> From: Dan Allen [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 02, 2004 10:46 AM
> To: Struts Users Mailing List
> Subject: never, ever bury an exception!
>
>
> I know that this might be obvious, but I am telling you all just so
> that you can learn from my
6 matches
Mail list logo
