But you would recreate only those services that you need right now. All other "heavy" services are created later on demand.
On Wed, Aug 11, 2010 at 11:53 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Wed, 11 Aug 2010 18:51:44 -0300, Igor Drobiazko < > igor.drobia...@gmail.com> wrote: > > Why not? How expensive is it to reload all the implementations? >> > > I think the issue here is not how expensive it is, but the state of the > services. I guess it's quite likely for an application to have services that > aren't meant to be reinitialized all the time, specially when they do some > costly operation in a constructor, for example. > > -- > 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 > > -- Best regards, Igor Drobiazko http://tapestry5.de
