I think it is safe to say that every developer's desire is to create bug-free, beautiful code that never fails. Some of us might be able to attain such lofty goals (not me). Hopefully those of you who write code this way are paid a lot of money to do so. For the rest of us, we need systematic error handling to make it appear as though we have written bug-free beautiful code that never fails.
But how do we implement such a solution in Fusebox? In the past, I have mentioned using a global error handler in the form of <cferror> in the index.cfm. You could also wrap the <cfinclude> of the core file in a <cftry>/<cfcatch>, but that doesn't provide circuit-level granular error handling. Fusium's FEX Integrated Error Handling is the answer. http://fusium.com/go/fex/ Take a look at FEX - it's a free, and was developed by me and Erik (we're Fusium). The FEX core file is fully compliant with the existing Fusebox core files, and should be compliant with a produced Fusebox specification, once one is established. It adds an error handling file called FEX_errorCatch.cfm in each circuit, and adds a few variables to the Fusebox API. FEX has been used in production by a few members of the community already, including me and Erik, for client's applications. This is not an official release. This is not a "Fusebox Council" release. By using the FEX core, you won't be compliant with the Fusebox "spec" as it exists in the fusebox.org core files. This is not an attempt to subvert the government process - we are exploring what we can do with Fusebox, and that meant trying something new. We look forward to the continued maturation of official Fusebox under the guidance of the Standards Committee. Thanks, NAT p.s. Look for more releases from Fusium in the coming days! ==^================================================================ 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 ==^================================================================
