Stephen McConnell wrote: > > Berin Loritsch [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 12 April, 2001 15:11 > > To: Avalon Development > > Subject: Re: [vote] lifecycle exceptions > > > > > > Peter Donald wrote: > > > > > >|-- ContextException <-- ContextualizationException // new; > > > >have both or > > > >have one...which one? > > > > > > What Berin said > > > > > > ContextException if Context.get() raises it else > > ContextualizationException > > > > What is the source of the error? Is it that the Context fails while > > attempting to retrieve an object, or is it that the Component can't find > > an object it is looking for? > > > > If it is the previous: ContextException > > If it is the latter: ContextualizationException > > My understanding is that this is an exception raised as a result of > executing or attempting to execute the contextualization phase and that > ContextualizationException can be raised in event of things like (a) > insufficient context information, (b) conflicting context information, (c) > internal problems established by an implementation when dealing with > supplied context information. As such this should be named > ContextualizationException and not ContextException.
Cool. Gotcha. This is good stuff, and should make it in the Javadocs for the class. Now I know where you are coming from. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
