RE: Overhead and Best Practices

> Exceptions derived from RuntimeException? At the JVM level 
> that really doesn't make any difference. The biggest expense 
> is in the collection of stack traces, but there is a lot of 
> other overhead as well (and .NET exception handling is slower 
> than Java exception handling anyway).

Since exceptions are very expensive in Java anyway, one would expect a
well-tuned application to be restrained in their use, so an additional
overhead shouldn't make too much difference overall.

Mind you, I was surprised to discover recently that the overhead is in
creating the exception, not in throwing it. There are a number of places in
Saxon where I create and save exceptions to be thrown later if things go
wrong, and that appears to be bad practice. I guess I should be saving an
exception factory instead!

Michael Kay
http://www.saxonica.com/



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642