OK. I now realize I should have been more clear. In CF5 I had an error
handler in the form of custom tag where I would dump out the cfcatch and
error "scopes." However, since this action could take place in custom tags,
I would first search to see if the cfcatch variable was available locally.
If it was not, I would reference caller.cfcatch as a backup. When I tried
to create a similar error hander in a CFC, I found that the only thing I
could access in the variables scope inside the CFC was "variables.this."
The cfcatch and error "scopes" are actually in the variable scope of the
calling page. So my question was really if there was any technique similar
to that of a custom tag where I can access the variables scope on the
calling page, without having to explicitly pass this in to the CFC. As far
as I know, every other scope is available from within the CFC, but the
variables scope is where all the error information is.
Thank you,
Mike Chabot
At 08:37 PM 8/5/2004, you wrote:
Hope that was what you were asking as like Gary, found it a little
difficult to get a clear picture as to what your objective is.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
