Hi Justin,

That's exactly the kind of thing I want to do.  However, I just tried to
use the manager app to restart my failed "Hello" example.  When the
context was up, the reload worked fine.  However, when the context died
because of an intentional error in web.xml, I get an error from manager:

FAIL - Encountered exception java.lang.IllegalStateException: Container 
StandardContext[/jas/example2] has not been started

Any ideas as to what the problem might be?

Thanks..

Jason.

On Mon, 1 Mar 2004, Justin Ruthenbeck wrote:

> At 12:50 PM 3/1/2004, you wrote:
> >On Mon, 1 Mar 2004, Shapira, Yoav wrote:
> > > >
> > > > Don't be so sure ;)  You can use the manager webapp (either
> > graphically
> > > > or via ant), you can write some custom JMX code in another webapps,
> > or
> > > > you can restart the server, but there are no other options.
> >
> >... the problem is that I'm trying to run one tomcat server for a large
> >group of students.  I can handle the deploy/undeploy part, but if a
> >student makes an error in their web.xml file, which is bound to happen, I
> >don't want to have to restart the server.  I'll need to look at a way to
> >wrap the reload via the manager application from ant. *sigh*
>
> You don't need to restart the entire process -- you just need to (as you
> mentioned) reload whatever context is unavailable.  Obviously you don't
> want to give every student permissions to restart every context, so
> that's out of the question.  It sounds like you're considering wrapping
> the ant reload with your own framework to check credentials before
> issuing the reload command (or something similar)?  If so, I would highly
> recommend starting from the tomcat <reload> ant task source code --
> you'll find it pretty straight forward to put something like this together.
>
> justin
>
>
> ______________________________________________
> Justin Ruthenbeck
> Software Engineer, NextEngine Inc.
> justinr - AT - nextengine DOT com
> Confidential. See:
> http://www.nextengine.com/confidentiality.php
> ______________________________________________
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to