> But realistically, I'm with Eddie -- what logging can you really
> apply consistently and automatically in a way that is more useful
> than noisy? If you have a bunch of fairly repetitive stuff
> spit out, then finding the real information is fairly tedious.
I also agree with it. I'm only looking for a temporary solution before
I implement a fine grained and well thought of logging for the
application.
> On the other hand, I don't find it all that burdensome to
> establish a
> static log instance for each class and toss around a few
> log.debug(...) lines, especially when I'm working on figuring out
> someone elses ill-documented code!
Hmm.. It appears to me that there are no frequently used or
established patterns for my requirements. May be I should also divert
my efforts into the same directions as mentioned by you. Can you or
someone suggest something for my requirements? My experience with
struts is relatively intermediate and we do not have any Tech.
consultants or Architects for my project.
Thanks and Regards,
Kinjal Sonpal
----------------------------------------
"In the real world, the right thing never happens in the right place
at the right time. It is the task of journalists and historians to
rectify this error."
--Mark Twain
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
