This means when I configure it like this it makes no difference to just deploying the same application twice with different paths, right?
My problem is that I have parts of my application which are restricted and I just want to filter the path requests with the httpd server which sits in front of tomcat so that I don't to configure any additional realms. -Pete > -----Ursprüngliche Nachricht----- > Von: Caldarale, Charles R [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 2. November 2006 15:27 > An: Tomcat Users List > Betreff: RE: Multiple paths to one application > > > From: Andrew Miehs [mailto:[EMAIL PROTECTED] > > Subject: Re: Multiple paths to one application > > > > Doesn't this only work if your application replaces the 'ROOT' > > application? > > Correct. > > If you want two names for the same app, you could place an additional > <Context> element in conf/[engine]/[host]/[app2name].xml, with a docBase > attribute pointing to the app to be aliased. This actually gets you two > deployments of the same app, so singletons and static fields won't be > shared across them. That may or may not suffice. > > - 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 start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
