tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Todd <>
Subject Re: server/config discussion
Date Wed, 28 Jul 1999 17:56:38 GMT

cool. can you expand on this a bit more? i must admit that my
mind is presently focussed more at the "webserver.xml" (server
config) level vs the webApp(s) web.xml level but it is none the
less important.

how do you see this unfolding (web.xml and/or webserver.xml)?

do you see some functional overlap?

btw, i am working with my j2ee/ri colleagues and with tomcat
it is trivial to add a new context (webApp) at anytime. i'm
going to consider copying the tomcat "shutdown" code (which
is really just an rmi hook to the running http server) to
proto in a "readNewContext" type method. in short, adding new
contexts to a running tomcat is trivial ... now to flesh out
the api's to allow for more options.

- james wrote:
> Just to throw in my $0.02 worth at this point re: web.xml. I'd like to see
> this file optionally be obtained by running a WebApp servlet, hence
> defining scope for a WebApp.
> --
> dIon Gillard, Multitask Consulting
> Work:
> Play:
> ----- Forwarded by dIon Gillard/Multitask Consulting/AU on 24/07/99 12:09
> AM -----
> "the web.xml is the xml
> which is context specific. if your familiar with the jswdk
> WEB-INF/*properties today ... those will go away and be replaced
> with a WEB-INF/web.xml.
> this thread here is, in my mind, focused around server config
> (webserver.xml) but it should be aware of component configurations
> (web.xml) as an item on the radar but not perhaps in the center
> of the screen at the moment."
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message