That approach helps somwhat, but I am still compiling with a classpath of /application1/codebase for /application1 and /application2/codebase for /application2
This works great for all the 3rd party jars that I need relative to each application but the applications themselves have totally different codebases that are currently set in the classpath used in the startup.bat -----Original Message----- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 4:34 PM To: Tomcat Users List Subject: Re: Multiple webapps, multiple classpaths Put the dependent external jar files in /application1/WEB-INF/lib and /application2/WEB-INF/lib. Jeff ----- Original Message ----- From: "Ryan P. Davidsen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 10, 2002 4:14 PM Subject: Multiple webapps, multiple classpaths > I am currently deploying multiple tomcats for multiple applications (1:1) > such as: > > application1-->tomcat1 > application2-->tomcat2 > > I would like to share a single instance of tomcat but have multiple contexts > registered (/application1 and /application2) > > The problem is that application1 and application2 need to have seperate > classpaths (due to conflicting codebases). Is there any way to deploy > multiple contexts to compile from different classpaths? Right now my > classpaths are being set in the tomcat startup script - I would like to have > something like: > > <Context path="/Application1" docBase="D:\application1\root" debug="0" > reloadable="false" > classpath="D:\application1\codebase,D:\etc"> > </Context> > > Is there a way of accomplishing this some other way? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
