One of the techniques I use alot is to include a JSP at the bottom of every page that
is essentially a JSP Debugging page. This code mines all of the JSP objects and
displays all of the values. I can toggle on or off what I want to see and when I go
to production I either comment out the include or remove it. I also use log4j within
my JSPs so that I can include info, warn and debug output from the JSPs in my web app
log. Whenever I wonder what is going on in a page I uncomment the debugging include
and almost always this leads me right to the source of the problem.
cheers,
don jones
-----Original Message-----
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wed 11/5/2003 8:06 AM
To: Tomcat Users List
Cc:
Subject: RE: best way to debug JSP's ???
Hola,
>I hope this isn't terribly off topic, but I couldn't think of a better
>list...
No, it's not off topic. Best way to debug JSPs? Hmm, how about not use
any? Just kidding. (Partially).
- Have plenty of logging statements in the JSP, outputting various
variable values.
>(BTW, is there a way to get at the servlet that's generated by
compiling
>the
>JSP?)
It's in the $CATALINA_HOME/work/[engine]/[host]/[context] directory.
Yoav Shapira
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary and/or
privileged. This e-mail is intended only for the individual(s) to whom it is
addressed, and may not be saved, copied, printed, disclosed or used by anyone else.
If you are not the(an) intended recipient, please immediately delete this e-mail from
your computer system and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
