When a context is set with reloadable="true" and a change is made to one of the appropriate folders, causing a context reload, what is and isn't undeployed and redeployed?
I ask because, surprisingly, a static variable kept its state across the automatic reload. Is this expected behavior? I thought it would be a completely fresh, new deployment that's the equivalent of stopping and restarting the server, with regards to the context with which you're working. However, stopping and restarting the server does, of course, clear the static variable's state, but that's not the case with the automatic reload - or am I probably just doing something wrong? Thanks. -- View this message in context: http://www.nabble.com/What-gets-reloaded-on-Tomcat-automatic-reload-tp14306781p14306781.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
