On Tue, 26 Nov 2002, edgar wrote:
> Date: Tue, 26 Nov 2002 14:47:00 -0500 > From: edgar <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: 'Struts Users Mailing List' <[EMAIL PROTECTED]> > Subject: RE: Tomcat Freezes when an Action or ActionForm is updated > > Craig happened to point this out that Tomcat will reload automatically > now: You can indeed configure auto-reload -- you specify how many seconds in between checks (Tomcat runs a background thread to actually perform them). However, that's not my favorite approach when developing a webapp. Instead, I set up the Ant build.xml file for my webapp to use the custom Ant tasks that are shipped with Tomcat 4.1 (documented on the manager-howto page). I create targets for "install" and "reload" that are dependent on the "compile" target, and an "unload" target for when I'm done. Now I fire up Tomcat (if not already running like it usually is), and my development cycle goes like this: (0) ant install (1) test the app (2) modify something (3) ant reload (4) still testing ? goto (1) : goto (5) (5) ant remove I find it much more effective to reload on command, rather than wait some arbitrary number of seconds at step (3) for the container to notice that something changed. Note that this works whether or not you actually configure the webapp as reloadable or not. The top-level build.xml file in the Struts distribution has targets like this for each of the webapps included with Struts (i.e. "install.documentation", "install.example", and so on) that you can use for examples. For this to work, you need to copy the catalina-ant.jar file (included in Tomcat's server/lib directory) to your $ANT_HOME/lib directory. Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
