This is a multi-part message in MIME format.
------=_NextPart_000_004E_01C02FE0.BF9D22E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In many ways, app_globals.cfm equals to application.cfm. But they are =
different in that application.cfm IS GURANTEED to run before a =
ColdFusion template but app_globals.cfm is not. You might think of =
application.cfm as a system controlled cfinclude, where app_globals.cfm =
is just a manual cfinclude. There are certain scenarios where codes in =
a ColdFusion template will get processed first before app_globals.cfm.
This was confirmed by my attempt to implement CF 4.5's CFERROR tag in =
app_globals.cfm for a site wide error handler. I noticed that there =
are certain errors that would abort the entire execution before =
app_globals.cfm even got called, so CFERROR tag was not processed and CF =
did not know how to handle the error, but simply defaulted to the Cold =
Fusion error page.
The workaround we are experimenting was to use application.cfm at the =
home level in addition to app_globals.cfm and place CFERROR tag in =
application.cfm. However, errors in custom tags still don't get caught =
by the CFERROR template because application.cfm does not get executed =
with custom tags.
Does anyone have better ideas ?
Thanks.
Jie-hong
[EMAIL PROTECTED]
------=_NextPart_000_004E_01C02FE0.BF9D22E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>In many ways, app_globals.cfm equals =
to=20
application.cfm. But they are different in that =
application.cfm IS=20
GURANTEED to run before a ColdFusion template but app_globals.cfm is=20
not. You might think of application.cfm as a system =
controlled=20
cfinclude, where app_globals.cfm is just a manual cfinclude. =
There=20
are certain scenarios where codes in a ColdFusion template will get =
processed=20
first before app_globals.cfm.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>This was confirmed by my attempt to implement CF =
4.5's CFERROR=20
tag in app_globals.cfm for a site wide error handler. I =
noticed that=20
there are certain errors that would abort the entire execution before=20
app_globals.cfm even got called, so CFERROR tag was not processed and CF =
did not=20
know how to handle the error, but simply defaulted to the Cold Fusion =
error=20
page.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>The workaround we are experimenting =
was to use=20
application.cfm at the home level in addition to app_globals.cfm and =
place=20
CFERROR tag in application.cfm. However, errors in custom =
tags still=20
don't get caught by the CFERROR template because application.cfm does =
not get=20
executed with custom tags.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>Does anyone have better ideas =
?</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>Thanks.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>Jie-hong</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2><A=20
href=3D"mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A></FONT=
></DIV></BODY></HTML>
------=_NextPart_000_004E_01C02FE0.BF9D22E0--
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
