Credit where credit is due: I've borrowed a lot of great ideas from Guice. Initially, T5 IoC started as just a better HiveMind, but the influence of Guice really pushed the envelope in a number of ways. Guice, coming in new and based on generics and annotations, had a large number of innovations.
We disagree on a number of crucial ideas including certain aspects of scope and lifecycle, the need for service contributions (something none of the other IoC containers seem to "get") ... but Guice pushes the spectrum of finding matches based on type and annotations. On 10/29/07, Thiago H de Paula Figueiredo <[EMAIL PROTECTED]> wrote: > > On Mon, 29 Oct 2007 16:28:33 -0200, Jan Vissers <[EMAIL PROTECTED]> > wrote: > > > Partially inspired by a question/some work by Leon Pennings (on this > > list), partially because of my interest in Guice - > > What exactly makes you interested in Guice? As far as I know (but I > haven't taken a look in Guice for some time already, so I can be wrong), > Tapestry-IoC does (almost) everything Guice does, but better. One of the > reasons is that T-IoC needs no annotations in your beans. :) > > -- > Thiago H. de Paula Figueiredo > Desenvolvedor, Instrutor e Consultor de Tecnologia > Eteg Tecnologia da Informação Ltda. > http://www.eteg.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind
