Sorry, I wasn't clear. tomcat.sh takes the classpath from the launching
environment and prepends lib/tomcat.jar to it. My original patch added this
functionality to tomcat.bat. However, if it's a desireable feature to start
with an empty classpath, and I agree that it is, the tomcat.sh should be
fixed so that it sets the classpath to just lib/tomcat.jar.
tomcat.sh and tomcat.bat should be functionally equivalent, at least to the
extent that the windows shell allows.
> -----Original Message-----
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 19, 2001 8:46 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [PATCH] TC3.3 tomcat.bat doesn't pick up
> external CLASSPATH
>
>
> >Ah, then you'll be wanting the contrawise patch to tomcat.sh
> >
>
> I'm not sure to understand perfectly what you say but with
> the new schema loader you start with an empty CLASSPATH.
>
> Depending where are located the .jar, you make them available
> to container (tomcat), webapps or both. Usefull to fix the XML
> parser conflicts....
>
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named. Any use, copying or disclosure by any other person is strictly
prohibited. If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
