Now the CFERROR tag allows you to specify a template that can actually "Run"
Cold Fusion tags and functions. This is not the case for the 4.0 version of
the tag.
In previous versions you are limited to these "variables"
Standard CFERROR variables:
Error.Diagnostics
Error.MailTo
Error.DateTime
Error.Browser
Error.RemoteAddress
Error.HTTPReferer
Error.Template
Error.QueryString
----------------------------
I guess what makes it "Structured" is the fact that you can specify the
"exception" you want to handle?
> Cool site, I didn't know of the cfhub site. Thanks.
>
> Although, I'm curious what is different in those pages than something
> I would have been able to implement in CF 4.0. Did the CFERROR tag
> not exist in previous versions? What makes error handling 'structured'
> vs 'unstructured'? Or am I just being way too anal about terminology?
>
>
> Joseph Thompson wrote:
> >
> > The new "Structured" exception handling allows you to set up a "global"
> > error handler (in your Application.cfm file) that is triggered for
"errors
> > and/or exceptions".
> >
> > You can specify an error template that will have access to all the CF
> > tags/functions in addition to the "standard" error messages that will be
> > triggered by both "regular" errors, and/or errors "caught" by
CFTRY/CFCATCH.
> >
> > umm... maybe my (8 page) explanation at chfub is better?
> >
> > http://cfhub.com/advanced/error_handling/
> >
> > > What exactly is Structured Exception Handling? It's listed in the
> > > docs as 'new in CF 4.5' but I cannot find any other information
> > > about it.
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
