Try either touching your appengine-web.xml file or hitting /_ah/reloadwebapp. Either of those should do a hot reload of your webapp. We haven't seen a lot of requests for webapp hot reloading, because the dev_appserver is usually very fast to boot. What is it that you're doing that would save a lot of time with a webapp reload but not be fast from a server boot? Can you let us know if this does indeed work and save you significant time?
On Fri, Aug 28, 2009 at 5:54 PM, Klaro <[email protected]> wrote: > > The Servlet Engine in the SDK translates JSPs right after they were > changed - fine! > > When changing Java code (such as a Servlet), the changes are not > redeployed - bad! > > So I have to stop and start the local Servlet Engine to see the > effects of the changes in my classes. This leads to hardly acceptable > turn around times. > > My question: Is there a trick or even an official configuration option > to deploy/reload classes immediately without restarting the server? (I > was using Tomcat previously, and there is some configurtaion option in > the server.xml.) > > Regards, > Klaro > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
