Hi Toby, thanks for your answer - I nave no time to try this right now. Will check it tomorrow.
It's nothing big or special that I would like to do - I have a few servlets that help serving a relativly small personal website, such as user login, reformatting/beautifying xhtml, a very special RSS reader and stuff like that. I want/need to port this to run in Google App environment, especially using the services such as Google User Accounts. You're right: the dev app engine does start fast, that's not the point. To restart it (using Eclipse) I need to stop it first (one click on red button) an restart it (another click on green arrow) after I saved my Java source file(s). I hate being interrupted with using my mouse for this kind of repeating & annoying button clicks while developing software. In my "old" environment with Tomcat, I had a configuration where the servlet engine was recognizing changes after a few seconds not only for web.xml, but also for classes/resources managed by it. So I could concentrate on my programming work. In Tomcat, this is a configuration option in "server.xml" (as far I can remember) and could be switched off since monitoring time stamps of files costs a little of performance. I will you let know if your hint is working - probably tomorrow... If it works as you say, you could offer an option like "touch 'appengine- web.xml' after compiling classes to force redeploy of Web application"... With Tomcat, the this mechanismen was undeploying the web application, but the redploying was after the first request (means: not immediately), so I had the chance to change more than one class without provoking a redeploy on every save action. Wow, this was a long anwer... Thanks again for your hint. Regard, Klaro On 29 Aug., 00:09, Toby Reyelts <[email protected]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
