make it into a variable structure to pass.
So, it looks like so:
<cferror type="exception" exception="ldap" template="/ces/error_ldap.cfm"
mailto="[EMAIL PROTECTED]">
Here's an example of the throw tag:
<CFTHROW
type="ldap"
MESSAGE="LDAP server down."
DETAIL="It appears the the LDAP server is not up and running or cannot
be connected to! Please try again or contact the system administrator for
help.">
(Don't anyone jump on me for wording of the detail. It's not my wording. I
KNOW my users don't know what an LDAP server is. :) )
Quite simple, but I would imagine you could use variables to determine which
error template to call.
-Deanna
----- Original Message -----
From: "Kevin Marino" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Tuesday, December 23, 2003 7:56 AM
Subject: RE: Error Handling
> Deanna,
>
> I assume you did something like this
>
>
> <cferror type="exception" template="ErrorHandler.cfm"
> exception="mycustom.exception">
>
> ....
>
> <cfthrow type="mycustom.exception" errorcode="6">
>
>
> Is that correct? Are you doing multiple CFERRORS?
>
> Thanks
> Kevin
>
>
> -----Original Message-----
> From: Deanna Schneider [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 23, 2003 7:57 AM
> To: CF-Talk
> Subject: Re: Error Handling
>
>
> Dave Watts wrote:
> > You can specify custom exception types, in which case you can catch them
> > with custom exception handlers. I haven't tried this with the CFERROR
tag
> > specifically, but according to the documentation you can specify custom
> > exception types for the CFERROR tag when using TYPE="EXCEPTION".
> >
>
> I've just recently tried this, throwing a custom error of type "LDAP" and
> providing a custom template to handle LDAP-specific errors. Works great!
>
> -Deanna
> _____
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
