Stephen McConnell wrote: > > Peter Royal wrote: > >>Sent: Thursday, 10 January, 2002 16:38 >>To: Avalon Developers List >>Subject: Re: Divergence from Avalon (was Re: [RT] Is Poolable Harmful?) >> >> >>On Thursday 10 January 2002 10:26 am, Berin Loritsch wrote: >> >>>This approach simplifies the use of the Component infrastructure >>>tremendously as we no longer have to have big complex try/catch/finally >>>methods to ensure that we release all components even if they are >>>ThreadSafe. >>> >>Are we going to make lookup() not throw a ComponentException >>anymore? If not, (or unless ComponentException extends >>RuntimeException) I don't see how the t/c/f block will go away, as >>you still have to trap the ComponentException.
No, ComponentException still exists. The t/c/f block goes away if we do not have to return any of the components back to the ComponentManager, and the method throws the ComponentException. >> >>On a side note, I always re-throw any ComponentException's as >>RuntimeException's, what do other folk do? >> > > I generally rethrow a qualified ComponentException (qualified in > that it has meaningful context in the exception message). > > Steve. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > . > > -- "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
