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? Regards, Carlos
On 9/2/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > in that case no clue. from the output looks like the wicket application is > being restarted? that means the servlet context is being > reinitialized...why > it would do that i dont know > > -igor > > > On 9/2/07, Carlos Pita < [EMAIL PROTECTED]> wrote: > > > > No, just a custom jetty launcher (I think it's based on your own code > that > > you kindly pasted in papernapkin a time ago :) ). Maybe the java agent > is > > being notified of the reloading classloader reincarnation after a > > monitored > > class changed and braindeadly reloads its configuration. It's not > causing > > a > > lot of overhead anyway. > > Regards, > > Carlos > > > > On 9/2/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > > > are you deploying on tomcat? i think tomcat monitors the dir and if it > > > > sees > > > a change it reloads the webapp. you can canfig it not to do that. > > > > > > -igor > > > > > > > > > On 9/2/07, Carlos Pita < [EMAIL PROTECTED]> wrote: > > > > > > > > Hi all, > > > > > > > > I'm using a tad of loadtime weaving in a very selective way: just a > > > number > > > > of classes in the service layer are being woven. For doing this, > > aspectj > > > > weaver is installed as a java agent and configured to monitor no > more > > > than > > > > the classes to advice. At the same time, some patterns are included > to > > > > drive > > > > wicket servlet reloading limited to the web layer. Both layers are > > > > deployed > > > > into disjoint packages. Regardless of this, each time I introduce > some > > > > modification into a, say, wicket page, I get the following log > output: > > > > > > > > [EMAIL PROTECTED] info AspectJ Weaver Version > DEVELOPMENT > > > > built > > > > on Monday May 21, 2007 at 13:36:36 GMT > > > > [EMAIL PROTECTED] ] info register classloader > > > > [EMAIL PROTECTED] > > > > [EMAIL PROTECTED] info using configuration > > > > > > > > > > /home/carlos/dev/java/eclipse/wicket-tests/target/classes/META-INF/aop.xml > > > > [EMAIL PROTECTED] warning ignoring duplicate > definition: > > > > > > > > > > > > > > file:/home/carlos/dev/java/eclipse/wicket-tests/target/classes/META-INF/aop.xml > > > > > [EMAIL PROTECTED] info register aspect > > > > web.aspects.SecureAspect > > > > ******************************************************************** > > > > *** WARNING: Wicket is running in DEVELOPMENT mode. *** > > > > > *** ^^^^^^^^^^^ *** > > > > *** Do NOT deploy to your live server(s) without changing this. *** > > > > *** See Application#getConfigurationType() for more information. *** > > > > > ******************************************************************** > > > > > > > > It is as if the weaver is forced to reinitialize itself or > something. > > Do > > > > you > > > > think this is normal or a symptom of ill configured classloaders? > > > > > > > > Thank you in advance. > > > > Regards, > > > > Carlos > > > > > > > > > >
