I'm relatively new to Avalon, but so far I like it.
I've noticed that Merlin is doing strange things for starting up my components - frankly I think the way it interprets the block.xml file is bizarre, but *someone* must think it's reasonable.
A block descriptor describes a deployment scenario - it does not imply
ordering with respect to the deployment solution.
What Merlin does is that it reads in all of the directives
(<component>, <container>, <include>, etc.), builds up a hierarchy of
containment and deployment models.
Once a valid model is constructed Merlin kicks in with the assembly phase during structural and runtime dependencies are resolved in order to establish a formal deployment and decommissioning sequence. When completed, the root block is deployed resulting in the ordered deployment of the components it is managing. If components in the sequence are composite, then your will see nested deployment sequences as the composite components deploy their internal implementations.
Stephen.
-- |------------------------------------------------| | 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]
