Greetings! Craig said...
>This kind of problem indicates that your Tomcat installation is somehow >corrupted. If it were really a bug, it would be happening to everyone, >not just to you. > >I suggest that you do the following: > >* Make sure you do not have anything in $JAVA_HOME/jre/lib/ext > (most *especially* not things like servlet.jar or j2ee.jar, > which are *guaranteed* to cause nothing but grief) RSH: WHY? That is where you put these files to allow you to compile code. Why should it cause Tomcat grief (esp. NOT 4.0 but only 4.0.1) unless the Tomcat jar loader code is now broken? > >* Do a clean installation of Tomcat 4 into a new directory. RSH: Done 3 times, downloaded new binaries 2 times, did binary comparisons of all copies of 4.0.1 - all the same every time. That is NOT the problem. > >* Make sure that all the examples work (including the ones that > use sessions) RSH: Which ones are the session ones? I tried 1/2 dozen examples, all worked. > >* Install your applications and test. We're now down to the simple servlet I sent to this list. Why doesn't someone with 4.0.1 on W2K compile it and try it. If it runs, then tell me which version of the Sun Java SDK you have, and what is inside .../jre/lib/ext ? And, if servlet.jar is NOT in that directory, how the heck did they get my servlet to compile with the SDK? (Using JBuilder is cheating<G>). -Richard > >Craig McClanahan -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
