Hi. On line 27 of cfa_throw.cfm we have the following description of the bAbort attribute. bAbort (boolean, optional) - if true, tag behaves like cfabort showerror. The error will be displayed and the template will abort. This is not completely true. <cfabort showerror> can be caught with <cftry> or <cferror>. Calling <cfa_throw> with bAbort=true will simply generate a <cfabort>. That is something completely different. A plain <cfabort> simply halts the template, without *any* exception handling taking place. This is a problem in that various other spectra tags like to call <cfa_throw> with bAbort=true. So if an error happens there, you have no chance to catch this, and the users of your app are left with an ugly message on their display. What I would like to see for the next version of spectra, or the community-source version of spectra, or whatever we get next, is for <cfabort> to be taken out everywhere and be replaced with something that can be caught. Give control back to the application. -- Michiel Boland <[EMAIL PROTECTED]> Digital Valley Internet Professionals Plantsoen 17, Wageningen, The Netherlands Phone: +31 317 465555, Fax: +31 317 460276 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
