> If you set up your application properly, you can run it in the debugger with > JDK 1.4. I know in Eclipse I can usually change the implementation of a class > and keep running. > > Please check the docs on disabling caching. By using this feature, you can > force Tapestry to reread all specs and reconstruct all objects every request > cycle. Slow, but not dreadful and any changes you make to specs or templates > shows up immediately.
This is exactly what I do and it seems to work great. For typical incremental development, you typically don't have to totally restart. The other thing I found very helpful is to run using a main class that just sets up Jetty rather than trying to stuff everything to a WAR and then deploy in something like Tomcat. Even if 1.4 can't do the incremental code patching, it only takes 10 seconds or so to stop, restart, and have the first page loaded again. -- Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
