Paul Singleton <paul <at> jbgb.com> writes: > Are you serious?! Our developers rely on Hot Code Replacement to > enable them to continue debugging after changes to program logic, > and only restart if they want/need to or if HCR fails (e.g. because > they added/altered a public member signature etc.). They would > not be happy with your policy!
I don't think we're talking about the same thing. I don't rely on the debugger as heavily as your developers. I like implement each feature bit by bit and test run each bit. This has nothing to do with the debugger. > Don't you run tests after changing your apps? If it doesn't reload, how can I run the tests? > I (think I) understand your Wish, but I reckon they way you work > is so unusual that you won't be able to rally much support for it. You mean that the reloadable flag is useless? Marty Hall strongly suggests setting it to true for development (ref: http://www.coreservlets.com/Apache-Tomcat-Tutorial). > In our apps, it's initialisation of the application bean that takes > time, and this happens at first request, not at reload. If for some reason you have to perform lengthy initialization, it may make sense to make the edit-reload-test cycle longer. However, this is just your case. There are many webapps under development that doesn't require length initialization. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
