-----Mensagem original----- De: Stephen McConnell [mailto:[EMAIL PROTECTED]
Its all possible now - but it would be better to wait just a bit until the resolution of the model versus runtime is out of the way.
Hey, getting in the middle of this discussion, correct me if I'm wrong, the process is:
1. Bootstraping Repository/Logging 2. Build composition.data from a serialized data (or XML) 3. build composition.model from data directives 4. Assemble the composition.model.ContainmentModel (the tree) getting the Appliances for any ComponentModel 5. Init the components marked with activation="startup"
Am I missing something?
Nope - you not missing anything.
This is a question concerning semantics of point 5. Currently when we deploy a component we invoke deploy against the runtime directly (the Appliance). Instead of this - the action of deploying needs to be applied to the model and its the model that then triggers an event which triggers a runtime adaption to the model state.
Stephen.
regards, hammett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | 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]
