> while at the same time coupling your application code to the underlying framework
Yes, its true. But if one bought the idea of using Avalon he/she must keep this in mind. The biggest downsize of avalon approach - to me - is to reuse avalon components in some scenarios that won't benefit from Avalon Framework. Hence my suggestion of supporting more that one IoC level (aaaghh) in Avalon# and maybe in others. > The benefits provided by the other two forms of IoC we will look > at next far outweigh those provided by this form of IoC. Bleh!! (c) Leo Simons This is biased. As you said there is not a good and a evil IoC implementation. regards, hammett > -----Original Message----- > From: Farr, Aaron [mailto:[EMAIL PROTECTED] > > Hello. > > Someone pointed this out over on the picocontainer lists. I haven't yet > had > a chance to read it: > > A Brief Introduction to IoC: > http://today.java.net/pub/a/today/2004/02/10/ioc.html > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
