other page actions:
Comparison between Guice, PicoContainer and Spring | Christian Schenk
comparison of guice, picocontainer and spring ioc
Inversion Of Control - Containers de Inversão de Controle e o padrão Dependency Injection :: JavaFree
te código de configuração é tipicamente feito em uma classe diferente. Por exemplo, cada amigo que usa meu lister pode escrever o código de configuração apropriado em alguma classe de setup própria. É claro que é comum manter este tipo de informação de configuração em arquivos de configuração separados. Pode-se escrever uma classe para ler um arquivo de configuração e ajustar o container apropriadamente. Embora o PicoContainer não contenha esta funcionalidade, existe um projeto relacionado, chamado NanoContainer, que provê os adaptadores apropriados para permitir que se tenham arquivos de configuração em XML. O NanoContainer interpretará o XML e então configurará o PicoContainer. A filosofia do projeto é separar o formato do arquivo de configuração do mecanismo interno.
PicoContainer: del.icio.us tag/picocontainer
IoC
Framework
picocontainer
Programming
pattern
martinfowler
Aslak Hellesoy's uncommon sense - The story of the PicoContainer
"Half a year later my colleague Martin Fowler wrote an article about the concepts behind IoC and PicoContainer, and this is how the term "Dependency Injection" was introduced. (Martin initially coined it "Service Injection", but Rod Johnson refined the term during a Geek Night in the ThoughtWorks offices in London). "
PicoContainer: del.icio.us tag/picocontainer
IoC
Java
picocontainer
Programming
opensource
codehaus
History
Google Testing Blog: To "new" or not to "new"... - Vimperator
Dependency injection asks us to separate the new operators from the application logic. This separation forces your code to have factories which are responsible for wiring your application together. However, better than writing factories, we want to use automatic dependency injection such as GUICE to do the wiring for us. But can DI really save us from all of the new operators?
Lets look at two extremes. Say you have a class MusicPlayer which needs to get a hold of AudioDevice. Here we want to use DI and ask for the AudioDevice in the constructor of the MusicPlayer. This will allow us to inject a test friendly AudioDevice which we can use to assert that correct sound is coming out of our MusicPlayer. If we were to use the new operator to instantiate the BuiltInSpeakerAudioDevice we would have hard time testing....
Page 1 | Next >>
