* Carlos Pita:
> That is the customary message the reloading servlet shows after
> reloading any changes. What is new is the output from the weaver
> above it. I guess the reloading classloader has to reinstantiate
> itself in order to load new versions of the same old classes,
> and this is notified to the weaver java agent so that it can
> take consecutive actions. But it's just a supposition. Maybe
> Jean Baptiste would be able to throw some light on the question?
Indeed everytime a monitored class changes, the application is
initialized and the ReloadingClassLoader is instantiated. There
is no other solution as there is no way to remove a previously
loaded class definition from the JVM's URLClassLoader, the whole
ClassLoader needs to be created anew.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
