Vjeran Marcinko wrote:
Hi people.
I am Fortress' user and I just took a first look at Merlin's docs on site. By Merlin way, any component's dependencies which are as usual mostly looked up in service() method now have to be also declared by meta data. This seems to me as certain overhead for developer, so just for curiosity can someone explain me the reasons for this kind of dependency definition ? I guess former containers somehow didn't resolve dependencies well although everything worked well for me till now with ECM or Fortress without these dependency definitions... maybe I just used them for simple cases where it worked ..?!
IOC
The objective is that the container supplies everything the component needs. To do this, the component needs to declare this. The big diference between Merlin/Phoenix verus Fortress/ECM is that the first group know in advance of component instantiation what the solution is wheras the Fortress/ECM is reacting to noise from the component. Ok - maybe that's a dramatic way of looking at it - but there are big advantages in knowing about component dependencies before instantiation:
* build time validation of deployment scenarios
* substantially reduced risk of runtime exceptions
* ability to resolve a provider in advance from a set of candidates and selection policy
* ability to control orderly deployment and decommissioning
Stephen.
Regards, Vjeran
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
