On CF5 (5,0,0,0) on WinNT(SP6) and Win2K(SP4), if a site-wide error handler has been specified in the CF Administrator, exceptions occurring in an Application.cfm do not cause the CF Server to stop processing - the CF Server calls the site-wide error handling and then processing continues.
As a simple test, I'm using a plain html doc as the site-wide error handler and in my Application.cfm I attempt to output a variable I know not to exist ("<cfoutput>#test#</cfoutput>"). I also have a test.cfm, which just outputs some html ("<h1>test</h1>").
When I request test.cfm, the code in the Application.cfm causes the site-wide error handler to be called, but then processing continues and the html in test.cfm is output.
Mark
-- These lists are syncronised with the CFDeveloper forum at http://forum.cfdeveloper.co.uk/ Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
CFDeveloper Sponsors and contributors:-
*Hosting and support provided by CFMXhosting.co.uk* :: *ActivePDF provided by
activepdf.com*
*Forums provided by fusetalk.com* :: *ProWorkFlow provided by proworkflow.com*
*Tutorials provided by helmguru.com* :: *Lists hosted by gradwell.com*To unsubscribe, e-mail: [EMAIL PROTECTED]
