On Thursday 10 January 2002 10:51 am, Berin Loritsch wrote: > >>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.
How far up the call stack would you recommend allowing ComponentException to go? Say I have a method doSomething() on a component that as part of running looks up another component. Should doSomething() then throw ComponentException? I view a failure in lookup up a component a runtime problem, similar to how the Context throws an IllegalStateException if you try to put() when it is read-only. I'm curious as to the design intent :) -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
