At 05:13 11/4/01 +0200, Leo Simons wrote:
>Okay. It seems there is broad support for the
>changes. I believe this is the setup that has
>the most support:
>
>RuntimeException
>^
>|
>CascadingRuntimeException // new
>^
>|-- StartException // new
>|
>|-- StopException // new
>|
>|-- SuspendException // new
>|
>\-- ResumeException // new
+1
>Exception
>^
>|
>CascadingException
>^
>|-- ContextException <-- ContextualizationException // new; have both or
>have one...which one?
What Berin said
ContextException if Context.get() raises it else ContextualizationException
>|-- CompositionException // new
Considering this is used by multiple things (Selectors as well) I think we
should stick to ComponentException
>|
>|-- ConfigurationException
>|
>\-- InitializationException // new
>
>interface Startable { // better name, anyone?
> void start() throws StartException;
> void stop() throws StopException; // new
>}
-1 Some things are startable without being stoppable and vice versa.
>interface Suspendable { // better name, anyone?
> void suspend() throws SuspendException;
> void resume() throws ResumeException; // new
>}
+1 if we can think of a better name.
>abstract class ClassImplementingAllLifecycleMethods implements
> Loggable
> Contexualizable,
> Composable, // name change
> Configurable
> Initializable
> Startable
> Runnable
> Suspendable
> Recontextualizable
> Recomposable
> Reconfigurable
> Disposable
>{
> void setLogger( Logger logger ); // does this need a different name?
Can you think of a better one?
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
