I recently upgraded from tomcat 3 to tomcat 4.1.12 and am having trouble
debugging new jsp pages as I add them. Whereas tomcat 3 would send the
error output of a jsp to the html page (making it easy to identify the
problem, fix it, and test it again), tomcat 4 sends the output to the
context's
Steven Peterson wrote:
what the error was. Is there any way to see the error output of a jsp
page without shutting down tomcat either by a) having the output sent to
the html stream; or b) having the log file accessible while tomcat is
running; or c) . . . ?
If you do your development on a
If you do your development on a Linux or Unix box, you can do b) with
tail -f logfile while Tomcat's running and writing to the file.
As far as I know, there's no way around the questionable file locking
semantics implemented in Windows
-Paul
If you install Cygwin on a Win32 machine,
