You could also wrap your included fuse(s) with a cftry/catch from within your fbx_switch. IMO, this allows you to wrap error handling around your actual website features instead of blocks of code that don't mean anything to the user. Be careful of writing too much code in your fbx_switch though, it will defeat the purpose if you get carried away. We try to restrict extra code in fbx_switch to error handling, and setting XFA's.
<cfcase value="ldapConnect">
<cftry>
<cfinclude template="queries/qry_ldap.cfm">
<cfinclude template = "dsp_ldap.cfm">
<cfcatch type="any">
<cf_error message="error connecting to ldap server">
<cfabort>
</cfcatch>
</cftry>
</cfcase>
Adam.
> -----Original Message-----
> From: Jeff Chastain [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 02, 2002 10:30 AM
> To: [EMAIL PROTECTED]
> Subject: Proper FuseBox Method
>
>
>
> I have an application where I am connecting to an LDAP server
> that is not the most reliable. Therefore, I want to be able
> to return an error code if the server is down or not
> responding. Now as far as FuseBox goes, do I create and send
> the error code in the query file where I figured out I cannot
> get to the LDAP server or do I have to tie in an action file
> that creates the error code?
>
> What is the proper "fusebox" method?
>
> Thanks
> Jeff
>
>
>
==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
