Niclas Hedhman wrote:
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...
Hi Niclas:
I don't see any benefit in deprecating this interface but I do see benefit in properly defining the framework contracts during the period bettween post-deployement and decommissioning.
Currently we have Executable and Startable as two post-deployment contracts. In the case of Executable it is a run once contract (at least in terms of container reponsibility) as compared to Startable which is a run until I tell you to stop contract.
One way of dealing with this is recognize that this is a family
of semantics that deal with post-deployment container/component
contracts and to deal with this at a metainfo level much in the
same way that the avalon-meta package lets us define what the
notion of contextualization means.
Lets call this phase "execution".
Can a compoent have more than one "execution" phase? In my opinion
the answer is no. If a component declares execution semantics, it
should be ONE clearly defined semantic.
* Executable -- run once
* Startable -- run until told to stop
* custom -- declaration of a execution handler
e.g. servlet semanticsStephen.
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
