The closest you're likely to get to what you want is the same as what
they use in the debugging templates:
<cfobject action="CREATE" type="JAVA"
class="coldfusion.server.ServiceFactory" name="factory">
<cfset cfdebugger = factory.getDebuggingService() />
<cfset events = cfdebugger.getDebugger().getData() />
Presumably you could keep retrieving the events query every time you
wanted to see the latest debug info and just read the new rows that have
been added.
I haven't tested this out, but it should be pretty simple to work out
for yourself.
The debug templates are in the WEB-INF/debug folder and are unencrypted,
so you can find out pretty easily where all the regular debug info comes
from by just looking at them.
Spike
Adam Cameron wrote:
You want access to whatever internal structures the cfmx runtime uses
to track the various data points needed for the debugging output.
Maybe. I'm not entirely sure what you mean, but it sounds about right
;-)
I just think - on long processes - it might be more useful to see some
of the debugging stuff as it happens, rather than after it happens.
Given CF has the stuff "in there somewhere", I was wondering if it was
possible to liberate it.
--
--------------------------------------------
Stephen Milligan
Code poet for hire
http://www.spike.org.uk
Do you cfeclipse? http://cfeclipse.tigris.org
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
cfcdev@cfczone.org 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/cfcdev@cfczone.org
