Keep in mind that the only classes that would be reloadable are servlets. Classes that aren't servlets will be ignored for reloading purposes.
I suggest you read up on the Tomcat manager app. It can stop/start/install/uninstall/deploy/undeploy your app without having to restart the whole server. Jake At 08:22 PM 10/11/2002 -0700, you wrote: >Hello, > >I have a server running Tomcat 4.0.4, with a multitude of Web >applications on top. Recently, reloading of modified classes >by reloading a Web app manually with the Manager Application >has stopped working. (Worked fine with 4.0.3) It's been a while >since we did the upgrade, so it could have been somthing else >that broke this. I tried setting up "reloadable" to true in the >application context, and that isn't working either! > >In any case, we are now forced to restart Tomcat for any updated >classes to be reloaded. When reloading our apps via the Application >Manager, the application log shows a succesful application reload, >but does not show the detection of any modified classes. > >We're running on Linux 2.4.7 kernel, Sun jdk 1.4.0_01 > >Any ideas? > > thanks! > > --G > > >-- >Guillermo Payet >O C E A N G R O U P >email: [EMAIL PROTECTED] >http://www.oceangroup.com >http://www.localharvest.org > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
