Yes, you need to reload the webapp for changes to be recognised, although for caching reasons, some browsers may not recognise the change to a JSP straightaway.
JSP's are compiled "on-the-fly" and compiled in the work directory as you mentioned. I use the ant build tool for this, I'm not sure what other alternatives are available. This is my understanding from looking at the log files. This is a typical entry when I reload a webapp: 2004-03-30 13:29:08 StandardContext[/gfapp]: Reloading this Context has started 2004-03-30 13:29:08 WebappLoader[/gfapp]: Deploying class repositories to work directory /usr/local/tomcat/work/Standalone/www.thegoldenfreeway.com/gfapp 2004-03-30 13:29:08 WebappLoader[/gfapp]: Deploy class files /WEB-INF/classes to /home/webapps/gfapp/WEB-INF/classes 2004-03-30 13:29:08 WebappLoader[/gfapp]: Reloading checks are enabled for this Context 2004-03-30 13:29:08 StandardWrapper[/gfapp:default]: Loading container servlet default 2004-03-30 13:29:08 StandardWrapper[/gfapp:invoker]: Loading container servlet invoker 2004-03-30 13:29:08 StandardManager[/gfapp]: Seeding random number generator class java.security.SecureRandom 2004-03-30 13:29:08 StandardManager[/gfapp]: Seeding of random number generator has been completed 2004-03-30 13:29:08 StandardContext[/gfapp]: Reloading this Context is completed 2004-03-30 13:30:08 StandardContext[/gfapp]: Reloading this Context has started 2004-03-30 13:30:08 StandardWrapper[/gfapp:jsp]: Waiting for 1 instance(s) to be deallocated 2004-03-30 13:30:09 StandardManager[/gfapp]: Seeding random number generator class java.security.SecureRandom 2004-03-30 13:30:09 StandardManager[/gfapp]: Seeding of random number generator has been completed 2004-03-30 13:30:09 ApplicationDispatcher[/gfapp] Allocate exception for servlet jsp On Wed, 2004-03-31 at 07:06, Rob Ross wrote: > I'm not talking about *restarting* Tomcat, I'm talking about *reloading* a > web app. You're right, you don't have to shut down the Tomcat server to > restart a webapp, you can just reload it, either manually by using the http > manager interface, or automatically by setting the "reloadable" attribute in > the config file to true. > > But for Tomcat to pick up changes to any files in WEB-INF/lib or > WEB-INF/classes, the web app to which they belong MUST be reloaded, whether > or you do so explicitly or have it done for you automatically. > > My question was, "what about JSP files?" and the original poster asked "what > about servlets?" Since servlets must live in WEB-INF, I'm *guessing* you > must also reload the web app if you want to pick up those changes to the > servlet. > > But I still don't know what is supposed to happen for JSP files. They must > be compiled to a servlet, but they get saved in the work directory, so they > could be handled differently, but I'm guessing, unless I hear something > definitive, that they too require the web app to be reloaded. > > Rob > > > > > -----Original Message----- > > From: Duncan Krebs [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 30, 2004 10:06 PM > > To: Tomcat Users List > > Subject: Re: restarting tomcat > > > > > > Rob, > > I know with using ECLIPSE and Tomcat4x you can run 'catalina > > jpda start' > > from a command prompt and be able to walk through your > > servlet code and make > > changes, recompile and run the updated .java file without > > having to restart > > Tomcat. This is very useful in a development environment. I > > don't see why > > this would not carry over to Tomcat5. > > - Duncan > > > > > > ----- Original Message ----- > > From: "Rob Ross" <[EMAIL PROTECTED]> > > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > > Sent: Tuesday, March 30, 2004 10:55 PM > > Subject: RE: restarting tomcat > > > > > > > > > > > -----Original Message----- > > > > From: Duncan Krebs [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, March 30, 2004 8:51 PM > > > > To: Tomcat Users List > > > > Subject: Re: restarting tomcat > > > > > > > > > > > > I also know that there are different types of debugging modes > > > > that you can > > > > run Tomcat it that do not require a restart for a .class > > file change. > > > > - Duncan > > > > > > Actually, according the Servlet 2.4 spec which I am just > > starting to read, > > > this should not be true. > > > > > > SRV.3.7 Reloading Considerations (page 33) states ... > > > > > > "...any such implementation must ensure that all servlets, > > and classes > > that > > > they may use, are loaded in the scope of a single class loader. This > > > requirement is needed to guarantee that the application > > will behave as > > > expected by the Developer." > > > > > > My understanding of this requirement is that there would be > > no way to > > reload > > > a single servlet separately from the other servlets in the > > same context - > > a > > > new Classloader would be created to load the new servlet, > > and all other > > > servlets/classes in that context. > > > > > > But since I just started reading this, maybe I'm not > > understanding all > > the > > > subtleties. > > > > > > Rob > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > --------------------------------------------------------------------- > 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]
