David, The documentation and what actually happens doesn't correspond, if I remember correctly the documentation says a reload with cause a fresh parse of the web.xml, the source code says otherwise. You'll need to remove the application, then create a new one for web.xml parsing to be done.
Regards, James Williamson www.nameonthe.net ----- Original Message ----- From: David Farb <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 12, 2002 4:07 PM Subject: Tomcat 4.0.3 manager reload bug? > My appologies if I sent this twice, I sent it as the body of the subscribe > originally, not sure if that works. > > In any case: > > When I use manager/reload?path=... it doesn't reparse web.xml, but does > reload classes. Am I missing something or ... Everything else I have done is > working fine. > > I am new to this, so its likely a configuration problem. First of all, let > me say that Tomcat is a TRUELY WONDERFUL PIECE OF SOFTWARE, THANKS TO ALL > WHO WORK ON IT!!! > > Relevant facts: > > - Running Tomcat 4.0.3 on Windows 2000 Professional. > - I created my own Service definition by copying relevent parts of others in > server.xml. (text available, but not included here to cut down on the size.) > - I use a different directory structure for my webapps than the one inside > Tomcat > - I copied the manager app directory (basically just web.xml in the WEB-INF > subdirectory) from the TomCat 4.0 webapps to mine. > - There are no configurations in my server.xml for applications, I rely on > the dynamic loading process where Tomcat loads anything as an application > which looks like one in the webapps directory, hence reloadable=true is NOT > set. > - Reload works always reports success, but changes to web.xml do not show up > (like adding a new servlet). > - Shutting down and restarting does reload web.xml (obviously) > - Installing a new .class file into the webapps directories DOES NOT show up > in the appllication unless a manager/reload is done. > > Conclusion: web.xml is not reloaded, .class files are. > > I have searched various online bugs and this email list and find no reports > of this problem. > > I suppose the real solution is to put the configuration in server.xml, but I > am reporting this anyway incase someone wants to fix it or it is a symptom > of a > more serious problem. > > This is not a major annoyance, just a minor problem. > > David Farb > > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
