Another great feature from Tapestry IOC is how easy is to write well designed applications using Design Patterns like Chains of responsibilities, Strategies or Pipelines. U will be able to write truly modular applications using them together with the Distributed Configuration mentioned by Thiago.
On Mon, Mar 7, 2011 at 7:56 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > On Mon, 07 Mar 2011 15:40:15 -0300, Lenny Primak <lpri...@hope.nyc.ny.us> > wrote: > >> Is there an executive summary of the differences or something like that? >> I am trying to decide whether to use Tapestry's IoC or J2EE CDI in my >> application. The only CDI I've used in the past is Google Guice. > > See > http://blog.tapestry5.de/index.php/2011/01/17/javax-inject-inject-support-in-tapestry/ > > Something very, very useful that Tapestry-IoC has that CDI, Spring and Guice > don't is distributed configuration. This feature is the reason Tapestry-IoC > was created instead of Tapestry (the web framework) adopt some other IoC > container. T-IoC has annotation-less injection, CDI and Guice doesn't. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
