Yes, log4j should be able to do this.
What you use try catch, along with log4j: Something like
<cftry>
// Do something that might break
<cfcatch>
<cfsavecontent variable="errorDump">
<cfdump var="#cfcatch#" />
</cfsavecontent>
<cfset logger.error(errorDump) />
<cfcatch>
</cftry>
Oh, and it's not a HTMLAppender, it's a HTMLLayout, used with
FileAppender or it's subclasses.
CFDumping the cfcatch will get you all the info that the cf error page
shows. It's just going to be formatted differently. If you want, you
could probably pinch the code that draws the gray box from the default
error handling template.
Adam Cameron wrote:
G'day mate
I don't think this is quite what I'm after (giving it a superficial
read).
I don't want to insert anything in my code to the effect of "here's a
milestone", or "here's an error"; I just want the debugging output (CF's
*own* debugging output) to go to a file AS IT IS GENERATED (as opposed
to at the end of the request, in the page-end output).
Or maybe log4j can be implemented to effect this, and I'm just not
seeing it?
--
Haikal Saadh, Applications Programmer
Teaching and Learning Support Services
K405, Queensland University of Technology, Kelvin Grove Campus
[EMAIL PROTECTED], 3864 8633
CRICOS No. 00213J
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
