Tomcat doesn't follow symbolic links by default. You have to enable this in server.xml for each Context where you want to use symbolic links. I'm not saying 100% that that was the problem, just that symlink support is not available out of the box with recent versions of Tomcat.
John > -----Original Message----- > From: Steve Hole [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 27, 2003 11:06 AM > To: Tomcat Users List > Subject: RE: Manual servlet deployment problems on 4.1.18 > > > On Wed, 26 Feb 2003 22:04:56 -0800 (PST) Steve Guo > <[EMAIL PROTECTED]> > wrote: > > > Steve Hole <[EMAIL PROTECTED]> wrote: > > This implies that the element defines the name of the > > web application? > > ------ what do you mean? the webapp is defined by the name > of the folder ("test") > > Ah! Which explains the problem. I will suggest that there > is a problem > somewhere in the JVM dealing with symbolic links to files > held on a SAN. > I'll have to try this on something other than Linux and see > if I still see > the problem. That's why it suddenly worked when I moved it > locally and I > thought it was because I had made a corresponding change in > the web.xml > file. > > Thanks for your help Steve. > > Cheers. > --- > Steve Hole > Chief Technology Officer - Billing and Payment Systems > ACI Worldwide > <mailto:[EMAIL PROTECTED]> > Phone: 780-424-4922 > > > --------------------------------------------------------------------- > 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]
