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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
