Have you considered that you can remove much of the dynamic config from conf\web.xml so that there is no default servlet or other dynamic behaviour in any webapp unless you explictly configure it so in the webapp's own web.xml?
In fact this is what I prefer to do myself (except on dev box because I use the manager webapp). My conf/web.xml is almost empty. that way, you can have a webapp which has none of the dynamic capabilities. > -----Original Message----- > From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] > Sent: Thursday 27 October 2005 19:21 > To: Tomcat Users List > Subject: RE: static server implementation? > > > > From: Robert Koberg [mailto:[EMAIL PROTECTED] > > Subject: Re: static server implementation? > > > > If you have a need for many virtual hosts, but do not need > > or want any ability for dynamic activity it would make sense > > to have a limited version of a tomcat host/context. I mean, > > I have a need to create VHosts from java, but those VHosts > > should not be able to affect anything (Read Only). > > I'm still not understanding why a standard Tomcat isn't > sufficient. If > you don't configure any dynamic content capabilities, none will > magically appear to thwart your goals. Are you concerned about > performance? Have you tested a static-only Tomcat to see if it's > adequate for your needs? > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE > PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete > the e-mail > and its attachments from all computers. > > --------------------------------------------------------------------- > 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]
