...... Original Message .......
On Wed, 10 Mar 2004 13:33:13 -0700 "Jonathan Hawkes" <[EMAIL PROTECTED]> wrote:
- Concerns like Creation/LogEnabling/Service/Initialize should have a
order
of execution.
They do. Concerns are evaluated in the order they are added to the container.
I agree. I think this would be a simplier and more natural method. It would also allow for the user to customize the lifecycle easily.
But what about shutdown lifecycles? There would need to be a distinction.
Just a thought - instead of looking at "shutdown" as a Concern within a queue, I figure one should adding a Startable concern - where the concern handles deployment and undeployment (starting and stopping respectively) in a sequence with other concerns.
Cheers, Steve.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
