atom feed10 messages in org.apache.tomcat.usersRe: Web.xml mistake results in <Conte...
FromSent OnAttachments
Kevin ConawayFeb 5, 2003 2:59 pm 
Will HartungFeb 5, 2003 3:37 pm 
Sean DockeryFeb 5, 2003 3:38 pm 
Kevin ConawayFeb 5, 2003 3:39 pm 
Sean DockeryFeb 5, 2003 4:18 pm 
Shapira, YoavFeb 6, 2003 6:25 am 
Kevin ConawayFeb 6, 2003 2:56 pm 
Craig R. McClanahanFeb 6, 2003 3:08 pm 
Sean DockeryFeb 6, 2003 3:32 pm 
Craig R. McClanahanFeb 6, 2003 3:46 pm 
Subject:Re: Web.xml mistake results in <Context> unavailable !?
From:Craig R. McClanahan (crai@apache.org)
Date:Feb 6, 2003 3:46:48 pm
List:org.apache.tomcat.users

On Thu, 6 Feb 2003, Sean Dockery wrote:

Date: Thu, 06 Feb 2003 16:33:03 -0700 From: Sean Dockery <se@sbdconsultants.com> Reply-To: Tomcat Users List <tomc@jakarta.apache.org> To: Tomcat Users List <tomc@jakarta.apache.org> Subject: Re: Web.xml mistake results in <Context> unavailable !?

Can you post an example reload task from a build.xml file?

It's all covered in the Application Developer's Guide shipped with Tomcat, and also online:

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/appdev/

Craig

At 15:08 2003-02-06 -0800, you wrote:

Enabling your students to issue a "reload" command on demand, via the manager webapp, would allow the turnaround time to be much faster -- indeed, I build that directly into my Ant build.xml files, so I can simply say

ant reload

which recompiles the app (because I made the "reload" target depend on the "compile" traget), and tells Tomcat to reload it, in one step.