[EMAIL PROTECTED] wrote:
> So, the safest thing to do is put everything under
> $TOMCAT_HOME/webapps/myTurbineApp/. This of course is not always
> practical and involves quite a bit of repetition.
If someone is going Servlets 2.2 he doesn't want his WAR to be dependent
on the appserver classpath, right? The repetition is unavoidable in
this case.
> But you
> definately should not have Turbine.jar or any of your application
> code in the system classpath when you start Tomcat.
If someone needs want to have more than one instance of Turbine per
machine, he can't put it in the system classpath because of the
sigletons.
> I usually keep
> a separate console (with a clean classpath) for starting and
> stopping Tomcat.
I would never use CLASSPATH in the shell. build/startup etc. scripts
set up the classpath explicitly for me. Othrewise it would be an
endless hassle...
> There was quite a bit of discussion (and
> confusion) on the Tomcat-dev mailing list a few months ago about
> classloader issues.
Yeah, this topic pops up on this list over and over again...
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
