That is assuming the manager application is enabled. I was hoping for more of an internal solution that Tomcat can do itself. This is being used in an educational environment and everytime a student blows up his context, he/she shouldnt have to run to the prof to reload the application...
Kevin ----- Original Message ----- From: "Sean Dockery" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, February 05, 2003 6:38 PM Subject: Re: Web.xml mistake results in <Context> unavailable !? > One of the following should work... > > http://localhost:8080/manager/html/start?path=/yourwebapp > > or > > http://localhost:8080/manager/html/reload?path=/yourwebapp > > This will prompt the Tomcat manager application to either start or reload > your application. > > At 17:59 2003-02-05 -0500, you wrote: > >In Tomcat 4.1.18, i have several different contexts each with a > >corresponding WEB-INF hierarchy and web.xml. Now, if I make a mistake in > >the web.xml like i forget to end a </servlet> tag, it says that there is a > >parse error and then "Marking this application unavailable due to previous > >error(s)" and I cannot use the context ever again until the server > >restarts. How can i fix this so the context gets checkd again at some point? > > > >Kevin > > Sean Dockery > [EMAIL PROTECTED] > Certified Java Web Component Developer > Certified Delphi Programmer > SBD Consultants > http://www.sbdconsultants.com > > > > --------------------------------------------------------------------- > 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]
