I really like the TapestryCoreServices idea. Inject one object and have access to all the core services.
This approach would make a lot more things more obvious in tapestry. I think tapestry is a little lacking when it comes to the obviousness of doing certain things. On Aug 24, 2011, at 10:05 AM, "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> wrote: > On Wed, 24 Aug 2011 10:50:54 -0300, Chris Poulsen <mailingl...@nesluop.dk> > wrote: > >> Hi, >> >> Can't you just inject it? >> >> @Inject >> private ServletContext servletContext; > > I like this idea, as we can already inject HttpServletRequest and > HttpServletResponse. :) > > -- > 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: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
