Re: what *really* happens when you reload or stop/start a webapp?
No, this is just an example. What I'd like to know is if stop/start or reload has the same effect on a webapp as actually shutting down tomcat and starting it back up. +jeff QM wrote: : would everything get dumped and reset -- would that static variable go : back to it's original state when the class file is first loaded? : : I should probably be asking a more specific question about classloaders : and sandboxes and whatnot, but I'm not sure how this stuff works in : tomcat and I'm not familiar w/ classloaders beyond their basic operation. I'm not familiar with how the manager app reloads apps, but you could perform an experiment to find out: If you already have such a static var in question, write a quick JSP that prints that value to screen. Fire up your app, hit this JSP (to catch the initial/default value). Call the servlet/whatever that changes that value. Next, reload Tomcat using the manager app. Hit the JSP again (make sure to force a reload in your browser). Compare the printed value to the original/default. Also, is there any reason you require this to be a static variable? -QM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: what *really* happens when you reload or stop/start a webapp?
I am pretty sure everything will return to default unless some save was committed but, someone else may give a more detailed explanation. Kind Regards Schalk Neethling Web Developer.Designer.Programmer.CEO Volume4.Development.Multimedia.Branding emotionalize.conceptualize.visualize.realize Tel: +27125468436 Fax: +27125468436 email:[EMAIL PROTECTED] web: www.volume4.com This message contains information that is considered to be sensitive or confidential and may not be forwarded or disclosed to any other party without the permission of the sender. If you received this message in error, please notify me immediately so that I can correct and delete the original email. Thank you. :: -Original Message- :: From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Barrett :: Sent: Wednesday, December 31, 2003 12:59 AM :: To: [EMAIL PROTECTED] :: Subject: what *really* happens when you reload or stop/start a webapp? :: :: I've got a web services application that I'm running w/ axis in Tomcat. :: According to the howtos for the manager stopping or reloading a webapp :: will make it unavailable and it will search for new files to load, :: specifically mentioning .class and .jar files. But does it go further? :: :: A more specific question: If I :: 1) had a jar in my webapp that had a class with a static field :: 2) set that static field to some value via interacting with my webapp :: 3) did a stop/start or reload :: :: would everything get dumped and reset -- would that static variable go :: back to it's original state when the class file is first loaded? :: :: I should probably be asking a more specific question about classloaders :: and sandboxes and whatnot, but I'm not sure how this stuff works in :: tomcat and I'm not familiar w/ classloaders beyond their basic operation. :: :: thanks, :: +jeff :: :: :: :: - :: To unsubscribe, e-mail: [EMAIL PROTECTED] :: For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what *really* happens when you reload or stop/start a webapp?
: would everything get dumped and reset -- would that static variable go : back to it's original state when the class file is first loaded? : : I should probably be asking a more specific question about classloaders : and sandboxes and whatnot, but I'm not sure how this stuff works in : tomcat and I'm not familiar w/ classloaders beyond their basic operation. I'm not familiar with how the manager app reloads apps, but you could perform an experiment to find out: If you already have such a static var in question, write a quick JSP that prints that value to screen. Fire up your app, hit this JSP (to catch the initial/default value). Call the servlet/whatever that changes that value. Next, reload Tomcat using the manager app. Hit the JSP again (make sure to force a reload in your browser). Compare the printed value to the original/default. Also, is there any reason you require this to be a static variable? -QM -- software -- http://www.brandxdev.net (C++ / Java / SSL) tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
