#error.rootcause.type# to pick the actual type of the exception, and then
process accordingly (redirect, email, just error to screen, log, whatever).
The 'rootcause' in there goes inside the CFErrorWrapper to the original
exception. I don't know how to do it directly in the CFERROR tag, but I've
not run across any downside to doing it this way. I'd actually even call it
a benefit, because then all your exception hanlding goes through a single
template, rather than multiple templates.
Cheers,
barneyb
> -----Original Message-----
> From: Marlon Moyer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 10, 2004 8:43 AM
> To: CF-Talk
> Subject: CFError bummer
>
> I had this great idea for my web apps. Anytime I needed to
> have a user
> authenticated, I'd check to see if the
> session.is_authenticated variable
> was set and if not, I'd throw a custom error type of
> "notLoggedIn". In
> my application.cfm file I'd have a cferror tag that would trap this
> error and send it to the login form. Then I found out it won't work.
> When you throw a custom error tag, CF puts it inside a
> coldfusion.runtime.CfErrorWrapper error type. This would
> still work if
> I also didn't want to trap notAuthorized errors, etc. also.
>
>
>
> Is there a way to trap the error inside the CFErrorWrapper object?
>
>
>
> --
>
> Marlon Moyer, Sr. Internet Developer
>
> American Contractors Insurance Group
>
> phone: 972.687.9445
>
> fax: 972.687.0607
>
> mailto:[EMAIL PROTECTED]
>
> www.acig.com
>
>
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
