Me:
> > myComponent.start(); // or should this go after getCommands()?
> > Iterator commands = ((Commandable)myComponent).getCommands();
> > for(commands.hasNext()) {
> > myThreadPool.add(new WorkerThread(commands.next()));
> > }
> > myComponent.run();
>
Berin:
> I aggree that the commands should be executed after the Component has been
> fully set up (that means after start()), and run then. I am not
> sure where
> the myComponent.run() comes from. The start() would tell the Component to
> begin (meaning background threads, etc).
It needs to be taken care of because it is/can be part of the lifecycle
process and it is possible for a component to implement both start() and
run().
Peter:
> interface Executable extends Startable, Stoppable {}
> interface Interruptable extends Suspendable, Resumable, Executable {}
>
> This would leave the issue more open for people who have done it that way
> in past.
-1
It will also mean it is a lot more likely that 'legacy' components will not
get updated. We're doing a major version change, and if we don't do it now
(remove Startable and Stoppable) it'll take a long time before we can.
Why that is bad? - management becomes more complicated than it has to be
and also less fail-safe.
A compromise would be to do it this way and deprecate Startable and
Stoppable
so they can be removed from 4.1. I personally would rather deprecate them
right
now and remove them from 4.0.
greetz,
LSD
<java:sig>
About LSD = new PersonalInfo();
LSD.name("Leo Simons");
LSD.email("[EMAIL PROTECTED]");
LSD.URL( [
http://www.leosimons.com, // personal website
http://www.atfantasy.com, // fantasy RPG portal
http://www.the-sign.nl // web-design company
] );
LSD.quote("Buh!");
email.setSig((String)LSD);
</java:sig>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
