When you mention the configuration to automatically reload the context, do you mean <WatchedResource>?
If you set reloadable to true in the context configuration, that should take care of WEB-INF/lib and WEB-INF/classes, and they don't need to be specified in WatchedResource - is this correct? Also, for static content like stylesheets that are within the WAR, a change to the stylesheet was immediately viewable in the browser - I found that surprising. Does Tomcat not do something like caching its static content and resources so that even if you change a file, that change isn't represented in the "work" folder? (I thought the concept of a work folder was essentially a cache... - if not, what is its purpose?) Thanks. Christopher Schultz-2 wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Lightbulb, > > lightbulb432 wrote: >> I noticed that in my exploded WAR file, if I make changes to a Facelet >> (similar to JSP) or stylesheet while Tomcat is running, I see the change >> when I navigate to that page in my browser. >> >> What changes are automatically picked up, and what requires a redeploy? > > JSPs (and probably related technologies) have their own ClassLoader and > the manager within Tomcat (or the component that manages them) generally > looks for changes, recompiles, and re-loads the individual page (or > whatever) without a context reload. > > All other changes require a context (webapp) re-load. > > Basically, unless your particular technology supports automatic > re-loading of the resource in question, you will have to re-load your > webapp. > > Tomcat, if configured to do so, will automatically re-load the context > if certain things change: WEB-INF/lib/*.jar, WEB-INF/classes/**/*.class, > and WEB-INF/web.xml will trigger an automatic re-load of the context. > There may be others as well (such as META-INF/context.xml). > > I believe that the only thing Tomcat can re-load without re-loading the > entire context is JSPs. If you are using another technology on top of > Tomcat (such as Facelets), it's up to that library to determine whether > this capability is available. > > - -chris > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGSzpV9CaO5/Lv0PARArnMAJ44GunwoN1EuaChr9R0fKpHC16JpACgr7/4 > /gfu4GPTUUpcdYw0oN3sUqQ= > =nhEc > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/What-changes-require-a-redeploy--tf3764471.html#a10646833 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]
