I put it in the db so that it can be analyzed at a later date for quality,
execs like to see fancy support stuff that really shows resolution, and in
group dev/support environments errors can be assigned and solutions tracked.
As Robert touched on - we log to a file - (uing log4j) that way if
I'm wondering what techniques people have used to do error catching and the logging of those errors to a DB.
Right now I wrap a CFC call with try/catch in my action template, if it fails I have a custom tag that is called that breaks the 'cfcatch' variable scope into it's parts and builds a
One method I've seen is to basically cfinclude the requested file in
the Application.cfm (then cfabort at the end of the file) and wrap that
in try/catch. I deal with a ton of legacy code, so I haven't tried
anything similar in Application.cfc, but I would imagine its would be
possible.
I've
why not use cflog? if you need to get the data into a db, you can do
it later using bulk loads from the files. you could also implement
log4j in Java if you need very sophisticated logging.
On 9/21/06, Brent Nicholas [EMAIL PROTECTED] wrote:
I'm wondering what techniques people have used to do
To: cfcdev@cfczone.orgSubject: Re: [CFCDEV] Semi-OT: Error catching and CFC's
One method I've seen is to basically cfinclude the requested file in the Application.cfm (then cfabort at the end of the file) and wrap that in try/catch. I deal with a ton of legacy code, so I haven't tried anything similar in Application.
