> > 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.
>
Well not that hard, Tomcat 3.3 by itself dont tries to respect your
classpath, but because the tomcat.(sh|bat) simply cleans classpath env
var before starting ( and recall it when it ends ) tomcat.., but by
itself dont takes any internal measure to do so, you can i.e construct a
classpath and modify tomcat.(sh|bat) shell command to start command with
a classpath of your own...
The thinking was "if you are someone that knows to have a classpath you
will knows too how modify tomcat.{sh|bat) to use it" to alleviate low
end user problems when first using Tomcat 3.3.
Your opinion is took into account for the 3.3 release..
Thanks for the feedback.
Saludos ,
Ignacio J. Ortega
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
