On 10/3/2003 at 14:57, you wrote:
DW> This is the expected behavior on CF 4 and newer versions. When you specify a
DW> site-wide error handler, it takes precedence over CFERROR TYPE="REQUEST".
DW> This is very good, as the site-wide error handler can actually do things,
DW> while the error page with CFERROR TYPE="REQUEST" can't really do anything at
DW> all - you can't use CFML tags or functions within that page. The site-wide
DW> error handler isn't a "default" error handler.
Thanks for setting me straight. That makes sense--though I am still
not sure why the site-wide error handler takes precedence over
CFTRY/CATCH error handling. Does it depend on the type of error that
occurs? I seems that CF should allow for local error handling and only
concern itself with un-trapped errors.
On one site I've got CFTRY/CATCH around certain database queries.
Under certain circumstances the queries may fail (it's a very large
Access db--I know...), in which case CATCH emails the error. Now that
I've implemented the site-wide error handler, the CATCH block gets
skipped in favor of the site-wide handler.
So, it seems that CF prioritizes as follows:
1. CFERROR - EXCEPTION
2. Site-wide handler
3. CFTRY/CATCH
4. CFERROR - REQUEST
~ Ubqtous ~
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
