Amen to that :-) So why not just use the deployment directory as the development directory? Edit your JSP, click browser's reload, done.
Yes, of course I thought of that, and also of just deploying the xml context descriptor with the docBase pointing to my build directory, just in case I preferred to keep it outside tomcat/webapps. But I'm asking about the way to deploy the app via the deploy ant task because it seems to be the recommended practice (according to http://tomcat.apache.org/tomcat-6.0-doc/appdev/index.html). So I'm not sure if that document is wrong regarding this task, or if it's outdated, or if I'm misunderstanding it (I mean, perhaps it doesn't really imply that the app won't be copied to webapps, but then how do you explain this affirmations?: # This action (depploy) does not require Tomcat 5 to be restarted, but it is also not remembered after Tomcat is restarted the next time. # Tomcat will recognize changes in JSP pages automatically (after just building the app, which copies modified jsps to the build directory) ). Best regards, Carlos On 1/4/07, Hassan Schroeder <[EMAIL PROTECTED]> wrote:
On 1/4/07, Carlos Pita <[EMAIL PROTECTED]> wrote: > Copy the entire app war, explode it, deploy it (and of course > recompile the requested jsp), > all that just to check, say, that a typo in the view was corrected or > that some cell contents are now correctly aligned? > It seems overkilling for checking tiny changes in jsps to me. YMMV, of course :-) -- Hassan Schroeder ------------------------ [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
