Alright, that worked. And changing the relative path to ../../../tomcat-4.1.x did not work either -- it did require the full, hard coded path. Why would that be?
Tom Veldhouse ----- Original Message ----- From: "Scott M Stark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 08, 2002 4:40 PM Subject: Re: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of the box. > Wrong, try reading the actual setting. As I stated I'm only using non-JDK 1.4 VMs. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > ----- Original Message ----- > From: "Thomas T. Veldhouse" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, October 08, 2002 2:29 PM > Subject: Re: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of the box. > > > > I think this is the reason: > > > > "The default value is that of the JBoss/Catalina bundle where the > > jakarta-tomcat-4.1.12-LE-jdk14 is included as jboss_dist/catalina." > > > > I don't think that does the non-JDK 1.4 crowd a lot of good ;) > > > > Tom Veldhouse > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
