"Craig R. McClanahan" wrote:
> 
> Stuart Thomson wrote:
> 
> > > 3) The new class loader scheme in this release ignores your CLASSPATH setting.
> > >    Instead, you are expected to add needed jars to Tomcat's "lib", "lib/common",
> > >    and "lib/shared" directories. See the "README" file in Tomcat's "doc"
> > >    directory for details.
> >
> > This will probably stop me from ever going to Tomcat 3.3. Finding
> > classes on the classpath is very convenient at development time.
> >
> 
> You will find that Tomcat 4.0 has a similar restriction -- the CLASSPATH environment
> variable passed in to tomcat.bat or tomcat.sh is totally ignored, and any user JARs 
>in
> the "lib" directory are automatically made available to all web applications.
> 
> Experience has shown that CLASSPATH problems account for nearly all newbie problems
> other than the ones related to mod_jk or mod_jserv (that means well over half the
> problem reports are related to this).  Having a clear policy on what is included 
>makes
> life much simpler for newcomers (who don't always understand what a CLASSPATH really
> does) to get set up.
> 
> People who know they want to include other things are also free to modify the 
>standard
> startup scripts -- but they are also expected to know enough to keep themselves out 
>of
> trouble.
> 
> Craig McClanahan

I can see the logic in ignoring the classpath in a deployment
environment. I also welcome the idea that servlets will not have access
to the implementation classes of the container. Although making classes
in the lib directory available to all could be a problem, what if a
servlet has e.g. it's own version of xerces in the war file. Will the
war file jars or the tomcat/lib jars take precedence ?

What I do very much like though, is in development time being able to
recompile one file, restart tomcat and have the change picked up without
having to rejar and redeploy. Sometimes I like to run a script which
points my classpath at different versions of the code and then restart
tomcat. In team
development we share a build of 1800 java files on a network drive. I
don't really want to copy all that under the tomcat directory every day.
If I can achieve this by modifying the scripts then that's fine.

Regards
Stuart

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to