-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
When distributing servlets to remote sites I am having
trouble diagnosing problems. In this particular case,
database items define the servlet's behavior and
appearance, so the system administrator really has
a lot of control, including control to mess things up.
I need some way to "trace" problems to help pinpoint
what is happening. I am tempted to put "lots" of debugging
type println's that can be turned on/off though a database
setting, but am having trouble accepting that inserting
tons of conditional messages throughout all the code
to do this is the right way to go about doing this. It is
going to mess up the code readability and mean lots
of "if" checking unnecessarily during normal production.
Can a few of you who have dealt with this issue shed
some light on successful techniques you have used.
Thanks for all opinions.
Frank Morton
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
