Hi, On one hand I can see that access to all services in ones IDE is a nice thought, on the other hand I fail to see how it would help you to pick the service you need; if you don't know what you are looking for...
Going directly into the javadocs and checking all classes that sound relevant may be just as good a strategy if you're lost and that would probably provide more value than trailing through a bunch of getters in the editor. On the other hand; if you know what you are looking for then you can usually just inject it instead of searching for services that provide it, inject the service and manually retrieve it. -- Chris On Wed, Aug 24, 2011 at 5:55 PM, Lenny Primak <[email protected]>wrote: > 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" < > [email protected]> wrote: > > > On Wed, 24 Aug 2011 10:50:54 -0300, Chris Poulsen < > [email protected]> > > 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
