Gang,
Is the Executable interface really well defined?
I think not.
This page doesn't even mention it; http://avalon.apache.org/framework/principals/lifecycle.html
Merlin tutorial docs says something like;
"If the Startable interface is not declared, but the Executable is, then the execute() method is called."
So, I would suggest that we either fully support it, or deprecated it...
THis is remnants of an idea long since abandoned. It was originally thought to have the Executable interface mean that the component would be run in its own thread--which could throw an exception (that would be neatly handled BTW).
The main issue was that we couldn't really make it part of the lifecycle and still have a clean and simply understood lifecycle model for the interface. It is unfortunate but understandable that we forgot to clean up that reference.
Instead, now that interface is used for thread pools and in GUIApp as the interface for commands. It still has value--but it is not meant to be part of the lifecycle.
I say we keep it, but fix the docs.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
