Eddie,
Thanks for your immediate and thorough reply.
> Possible? Yes ... but you're not going to get much
> meaningful information.
> IMHO, meaningful information comes out of exceptions, and I
> personally trap
> those and cause the app to show meaningful errors to the
> user. The best
> place to have logging is in your catch statements - be that
> in your actions
> or the classes that make up your model. It's so trivial to
> put in that
> there really isn't any excuse for not doing it right the first time.
Yes, exceptions truly are vital and I have them caught at almost all
appropriate places. However, what I'm looking at is a non-intrusive,
simple plugin kind of logging mechanism, only for the time being. We
generally work out our own APIs, instead of directly using framework
or technology specific APIS. By the time these are worked out, our
guinea pig users are going have a go at the application for functional
testing. I want to put some quick and dirty logging for them.
> I'll be surprised if there's a better solution that will
> give you meaningful
> feedback out of the logging (which is why you do logging -
> for meaningful
> feedback, that is - right?), but I have been wrong many
> times, and I don't
> think I've seen my last error yet :-)
That's true, but like I said earlier, I'm only looking at a quick and
dirty approach, so that I'll have some additional info alongwith their
feedback. If possible, please throw some more light for this type of
strategy. I'll be eager to hear from you and all the listers.
> Good Luck!
> Eddie Bush
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]
