Thats what cfthrow and cfrethrow are for.
Regards, Andrew Scott http://www.andyscott.id.au/ > -----Original Message----- > From: Claude Schnéegans <schneeg...@internetique.com> [mailto:=?ISO- > 8859-1?Q?Claude_Schn=E9egans <schneegans@interneti=71?= =?ISO-8859- > 1?Q?ue.com=3E?=] > Sent: Monday, 27 June 2011 11:06 PM > To: cf-talk > Subject: Re: application.cfm > > > >>Actually cfabort was introduced as a debugging tag. > > > Really? > Note that I use CFABORT because I was not sure CFCONTENT will cause > processing to stop. > It is not specified in the docs, but it does, so I could remove the CFABORT tag > after CFCONTENT> > > There is still a good reason for CFABORT: stop processing after displaying an > error message in application.cfm. > This is not debugging, but HTTP request validation. > I have plenty of validation done in application.cfm. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345818 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
