This solution works if you're front-ending with Apache- I have seen CGI/Perl do this to specifically route incoming requests to CGI/Perl site 1 to their folder (and consequent access to site2 to Tomcat)
Symlink is terminal specific setting up term access to symbols representing another folder .. Symlink is agnostic to which protocol is used to access port 8080 should route to Apache/Tomcat in that order with no proviso for security and consequent erroring by external programs that cant read a symlink (such as WinSCP) Caveat Emptor- M- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: "Brian Munroe" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org>; "Martin Gainty" <[EMAIL PROTECTED]> Sent: Wednesday, July 12, 2006 1:59 PM Subject: Re: Alias' and the like > On 7/12/06, Martin Gainty <[EMAIL PROTECTED]> wrote: > >> >> allows you to access seemlingly disprate sites thru Virtual Hosts check out >> http://httpd.apache.org/docs/1.3/vhosts/examples.html#serverpath >> > > I am pretty sure Alias will only work *if* you (Dave) don't need to > process it through Tomcat. It is shown in the mod_jk examples as a > way to link to static content, > > Just a total shot in the dark here (and probably really bad advice), > but how about a symlink in the webapps dir? > > admin -> services > > -- brian > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
