Tomcat should never crash when a webapp misbehaves, it should just stop
the webapp from doing any harm in the first place, it should just report
an error and then move on. Tomcat documentation shows how to configure to
serve virtuals, although its a little vague. What I don't understand is
why can't you map an app directly to a directory instead of having it
mapped to a base directory and then putting everything within the proper
place i.e.: /mapped_dir/WEB-INF /mapped_dir/WEB-INF/classes etc. etc.
The docs never realy explain as to why this setup was chosen instead of
the old JServ way of just telling where the servlet is or should be.
Jamie
On Fri, 3 Nov 2000, Joe Emenaker wrote:
> > From: "Rick Anderson" <[EMAIL PROTECTED]>
> > > The documentation for Tomcat seems to recommend that for a multi
> developer
> > > environment everyone run their own tomcat instance and each developer
> > > having their own server.xml file.
> > >
> > > Isn't there an easier and cleaner way of doing this?
> >
> > I'm currently running each of my sites with separate tomcats
> > with their own separate server.xml files, and I thought it
> > was actually a pretty clean way of doing it, particularly
> > for development, as everybody essentially has their own server
> > that they can use/crash/misconfigure without bothering anyone
> > elses work.
>
> Well, with each webapp getting it's own "/lib" and "/classes" directories
> and such (although this is part of the servlet 2.2 spec, so not unique to
> tomcat), tomcat has already gone a long way toward giving each development
> its own sandbox. About the only thing that I can think of off the top of my
> head that's still server-wide is the users/passwords. If tomcat could make
> that localizable, it seems that you'd only need to run one server. As far as
> users being able to crash the server without affecting anybody..... tomcat
> itself should crash when a webapp misbehaves.
>
> - Joe
>
