On Fri, 29 Mar 2002 16:44, Jeff Turner wrote: > In my case, I have: > > public class CascadingRuntimeException // in framework > > public class BufferOverflowException > extends CascadingRuntimeException // in Excalibur's collections package > > > I'd like to remove that dependence, since it's the only thing tying > collections to framework. The public interface will be identical, but > typecasts will break.
go for it. ExceptionUtil has recently been enhanced to use reflection to get at "cause" of exception if the exception does not implement CascadingThrowable. This was to ease integration with jdk1.4. However it is not turned on by default (I thought it may be a CPU hit) - maybe we should turn it on by default? Given that printing out the exception is likely to be more costly CPU-wise anyway. -- Cheers, Pete --------------------------------------- Be nice to your friends. If it weren't for them, you'd be a complete stranger. --------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
