I'm quite late to this thread, so I'll stick to answering the one technical question:
On Sun, Jan 23, 2005 at 12:03:36PM -0800, Dola Woolfe wrote: : the code changes, the app needs to be restarted. The : project I work with takes 2 min to start up so this is : prohibitive There's a "reloadable" attr on the Tomcat config's <Context> tag. Set this to "true" while you're in development mode to make the container periodically check for changes in WEB-INF/classes and reload accordingly. It may also check under WEB-INF/lib, I don't recall... : Sometimes for development purposes I dumb : it down so it takes 10 sec to start up but it is still : a pain. Am I saying anything that indicates that I'm : .doing things wrong? "Wrong" is too strong a term here; but some would argue that you may not have to tweak the servlets so much if you were to formally separate calls to business logic (servlets, which require a container restart) and formatting/presentation (JSPs, which are automatically rebuilt when changed). In my experience, the servlet layer is pretty thin and simple; it's getting the final content *just right* that can require several edits to a file. I don't mean for this to sound flippant. A lot of the good ideas and best practices are based on starting an app from scratch. When you're migrating an existing app -- and in your case, across two servlet spec revisions -- it can be tough. You sometimes have to decide whether it's worth a hefty refactoring effort or starting over from scratch. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
