From: "Joe Emenaker" <[EMAIL PROTECTED]>
> > 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,
>
> 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.
Perhaps I'm just being paranoid :) Since we are dealing
with separate virtual domains, I like to be able to shut
down/restart the tomcat for a domain if necessary without
having to disturb other domains. For instance, if we were
replacing a WAR for one site, I believe it is necessary to
actually shut tomcat down (from what I've read anyway, I
haven't actually had to do that yet).
In a situation where there isn't a problem with bringing
tomcat down for some reason, I might prefer to just run
one, since the multiple java sessions do tend to gobble
up lots of memory.
DK
