My startserver and stopserver work just fine (WinNT)... My first servlet worked first time (after I included servlet.jar in the CLASSPATH) However, I suspect the server (and not the browser) is caching the servlet and I end up stopping it and starting it (the server) just to see the new changes in the servlet. At first I thought it was the browsers (IE & NS) but I think I may have eliminated that possibility, but what do I know, I just started writing servlets a few hours ago... Is there a way to prevent caching by the server (if that's what it is?) Also, I saw somewhere recently that a META tag may help (at least with regular pages) with a "NO-CACHE" value or something like it... Thanks!
Tony Alicea Senior Java Web Application Developer, SCPJ2, SCWCD
I think you need something a little more industrial strength if your goal is to elimintate caching. JRun does a nice job of recognizing servlet updates and loading the newer servlet.