>From a quick peek... The ReloadableObjectCreatorSource creates the proxies (ReloadableServiceImplementationObjectCreator) which create the Service. Each ReloadableServiceImplementationObjectCreator implements UpdateListener which is called when it should check for changes / updates.
But you are aware live class reloading is only enabled during development right? Steve. On 16 June 2012 22:55, Thiago H de Paula Figueiredo <thiag...@gmail.com> wrote: > On Sat, 16 Jun 2012 10:56:10 -0300, Thim Anneessens <thimw...@gmail.com> > wrote: > >> Hello, > > > Hi! > > >> Singleton service reloading is unfortunatly not suffisiant for my purposes > > > Could you be a little more specific? This would help us to provide help to > you. > > >> so I was wondering if anyone could give me some insight on how Tapestry >> live class reloading works (whish are the classes involved in that process >> for instance). > > > I don't know the internals, but basically Tapestry-IoC (for services, > Tapestry-Core, the web framework, isn't involved) uses a proxy for every > single which is defined by an interface. For pages, components and mixins, > Tapestry-Core uses its own classloader. > > -- > Thiago H. de Paula Figueiredo > > > --------------------------------------------------------------------- > 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
