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 log file.  This would not be so bad, but the log file is
locked by my operating system (Windows 98 se) until tomcat is shutdown.
The upshot is that for every error, I have to shut down tomcat to see
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) . . . ?

Thanks,

- Steve Peterson

--
Steven Peterson, President
Frontier Productions, Inc.
310 Wesley Drive
Chapel Hill, NC 27516
http://www.frontierproductions.net
Tel: 919-942-1386
Fax: 919-933-2677



--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Reply via email to