Requirements, I understand. Now what do u mean by solutions ?
In the case of a dependency Merlin will automatically wire things together for you, however - sometime you want to override the things that Merlin does. This is achieved by declaring a <dependency> directive containing a definition of the <source> component address to use as the service provider.
The following examples should provide everything you need to know.
http://avalon.apache.org/merlin/starting/tutorial/dependencies/index.html
Cheers, Steve.
Thanks
Vikas
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 1:22 PM
To: Avalon framework users
Subject: Re: Dependencies
Vikas Phonsa wrote:
Hi Everybody
In the definition of <component> element of block.xml at http://avalon.apache.org/merlin/meta/block/components/index.html
<dependencies> nested element has been defined.
How is this element different from the <dependencies> element
automatically
generated in the classname.xinfo file for a component.
The definitions in the .xinfo file are the declaration of requirements. The definitions in the block are the declaration of solutions.
Cheers, Steve.
Or any comments regarding this ?
Thanks
Vikas
--------------------------------------------------------------------- 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]
