Accepted answer

a quick and dirty way to force tomcat to recompile/reload your pages is to delete tomcat's working directory. in my limited testing it works fine but obviously, i wouldn't recommend this in production. :)


i believe myeclipse, if configured correctly, will let you update applications running in tomcat without restarting tomcat. it is unfortunately a commercial product though.

oracle jdeveloper had a copy of oc4j bundled and it was possible to make changes on-the-fly without restarting the container, again this may not be possible given your environment.


if i'm not mistaken you can just copy your client-side changes (.jsf, .html, .css, .js) to the webapps folder of your application, whilst it is running. the jboss j2ee version of eclipse i'm using allows hot replacement of some java code.


you can use some other container, not tomcat, which not needed to be restarted when you make some changes in you project. it's can be jboss. also if you will use some tools, for example jboss tools, you develop much faster and easy :-) as for me, when you make changes just in .css or .xhtml page, you shouldn't restart tomcat, you should just republish you application. in jboss tools you can make it using jboss tools server view.


you should use dynamic web projects and tell eclipse java ee to deploy to a suitable tomcat instance. this will allow eclipse to help all it can (but that is still not blazing speed though).


put this in your web.xml.


this means : "how often will the app server recompile my jsp". the value is in seconds.


just in case you use maven to build your project, you can use this command line to test in tomcat:

mvn clean war:exploded tomcat:run

that will run a slim instance of tomcat (tomcat:run) taking the changes of your web files (.jsp, .html, .css, .js) directly from the source you're editing (war:exploded), so you'll just hit f5 in your browser

Related Query

More Query from same tag