Tomcat java development cycle too long - editing and testing. help!!

[A Ferrisini]

This is what i have to do when i am editing/testing my java code using the Tomcat server:
1) edit the code
2) delete current class files from server
3) restart tomcat server
4) attempt to access deleted files in browser
5) copy new class files from edited code
6) restart tomcat server
7) access new class files in browser
this is using servlets.
I want to be able to simply edit my code, build it, then restart tomcat and be able to view it. Or in fact not having to restart tomcat would be even better.
Any ideas??
Cheers,
RMP

[Barry Andrews]

Check out Ant
http://ant.apache.org/
You can set up a script to automate all this stuff, then just by typing one command your application can be built and redeployed.

[William Brogden]

Tomcat comes with a "management application" which is excruciatingly easy to configure - you can then unload and reload applications from a browser screen without stopping and starting the server.
I can't understand why people don't find this when they install Tomcat - it is sitting right there in the online documentation - /tomcat-docs/index.html will get it.
As Barry says, ANT will let you automate compiling, copying and etc. manipulations of files.
Bill