> -----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
>
I've read through it and thought everyone here would want to know about this
part:
"The fact that the Avalon framework has been providing an IoC framework for
several years now, without generating nearly as much interest in the idea as
either Spring or PicoContainer, is probably due to the downsides of this
approach. The requirement to implement specific interfaces can give code a
"bloated" feel, while at the same time coupling your application code to the
underlying framework. The benefits provided by the other two forms of IoC we
will look at next far outweigh those provided by this form of IoC."
And my response:
* Avalon, IoC, and other fun
2004-02-10 07:08:33 jaaron [Reply]
Wow, there's sure been a plethera of IoC articles going around. I
don't completely agree with your analysis of Avalon (though being an avalon
developer, I may be somewhat biased). There are advantages and disadvantages
to each approach.
I would also like to point out that IoC means a lot more than just
dependency management. It's a principle which covers many design patterns,
dependency injection being simply one. For more information, see some of the
links below:
http://www.jadetower.org/muses/archives/000020.html
http://www.jroller.com/page/lsd/20040122#ioc_dependency_management
http://www.betaversion.org/~stefano/linotype/news/38/
http://www.jadetower.org/spire/mutuals/
http://avalon.apache.org
J. Aaron Farr
� SONY ELECTRONICS
� DDP-CIM
� (724) 696-7653
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
