On Sat, 16 Jun 2012 12:52:24 -0300, Thim Anneessens
wrote:
Thanks for the reply Thiago,
You're welcome! :)
Singleton service reloading is unfortunatly not suffisiant for my
purposes
Tapestry service reloading works only on singletons and I need to have
multiple instances of the class I
>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
Thanks for the reply Thiago,
Singleton service reloading is unfortunatly not suffisiant for my
purposes
Tapestry service reloading works only on singletons and I need to have
multiple instances of the class I'd like to reload per thread.
I guess I could easely reload classes if I was notifi
On Sat, 16 Jun 2012 10:56:10 -0300, Thim Anneessens
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 o
Hello,
Singleton service reloading is unfortunatly not suffisiant for my
purposes 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).
Tanks in advance,
Thim.
---
