2010/11/17 Thangalin <thanga...@gmail.com>: > Hi, > > Judging by its name alone, I would have thought that "setclasspath" (.bat or > .sh) would be a place to put custom code that sets the classpath before > Tomcat starts, or stops. >
Setting CLASSPATH explicitly is a bad idea. The cases when it is needed in Tomcat are very very rare. > I recommend the following: > > 1. If a file is named "setclasspath", then the only responsibility for > that script is to set the classpath. > 2. Create a file named "setenv" and document (using REM statements) its > purpose. > > It appears as though "setclasspath" and "setenv" have had their names > swapped. > > -- > > I am writing a book that includes instructions on how to configure Tomcat > and JasperReports. It feels very strange to tell people edit a new file > called "setenv.bat" and put classpath changes there, while avoiding > "setclasspath.bat" (which was my first, yet incorrect, guess). > > Kind regards, > Dave Jarvis > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
