Hi Nader,
Here is my understanding of how it works:
Merlin looks at the provided block.xml file, and builds a list of components to deploy. These components come from the component declarations in the block.xml, the component declarations in any block.xml files in included blocks, and any components discovered in the classpath that are needed to resolve unspecified dependencies of those components.
The end result is a directed graph of components, where a component's dependencies are lifecycled before the component itself.
The other factor on whether a component is initially lifecycled is it's activation attribute. Components with activation="startup" are lifecycled automatically by the container on startup whereas components that are "lazy" are only lifecycled when they are requested.
So, looking at the block.xml you provided, it looks like Merlin would attempt to lifecycle the IMServer component on startup, which would trigger a chain of other components as IMServer's dependencies, and the dependencies dependencies and so on are lifecycled.
Hope that helps (and I hope its accurate ;-) ),
It's on the button!
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]
