Yes, I tried that. Whenever I changed a java file, the app context got restarted which was rather slow. Took 10 seconds for the app to be ready to use again. Is that what's supposed to happen? I was hoping for something like a one-second reload of just the one file that changed.
Patrick Casey wrote: > Did you set reloadable="true" in your web.xml? > > --- Pat > > > >>-----Original Message----- >>From: Bryan Lewis [mailto:[EMAIL PROTECTED] >>Sent: Monday, January 16, 2006 5:29 PM >>To: Tapestry users >>Subject: Re: First page display slowdown in v 4.0 >> >>I must be doing something wrong then. I've tried three app servers, >>currently trying JBoss/Tomcat. Running inside Eclipse, starting in >>debug mode. I have Tapestry's caching disabled in the startup >>properties, and changes to the html or page files do take effect >>immediately. But when I make a small change inside a Java method... it >>does get built automatically, and the class file does get updated in >>the webapp tree. But the change doesn't show up in the browser until I >>restart the server or reload the app. >> >> >>Alexander Varakin wrote: >> >> >> >>>Hot-code-replace feature is available in Eclipse if you run web container >>> >>> >>in >> >> >>>debug mode. The problem is that it takes twice longer to display first >>> >>> >>page >> >> >>>in debug mode. Also Hot-code-replace works only if you don't touch >>> >>> >>function >> >> >>>declarations. >>> >>> >>> >>> >>> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >
