Which is too bad, because redeploying a web app isn't the same thing as restarting a web app.
Specifically, if you have a bunch of JSPs already compiled (by the container), then redeploying will lose those compiled artifacts.
Yet, you need to use redeploy if you want to, say, reset an internal cache or do some other logic that "only happens at startup".
Not every application can use "precompile JSP" during deploy, sometimes it just takes too long, sometimes not every JSP in the system CAN compile (for whatever reason), and when that happens, the deploy fails (rather than just skipping the JSP and noting it).
So, anyway, for several reasons, it would be nice to be able to do a "restart" of a webapp which consists of the container shutting down the webapp (lifecycle events), obliterating its classloader, and reloading everything, while maintaining all of the server created artifacts.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=276822